Article summary
Review avatar, business status and mappings for shared Gibraltar business phones without binding a contact point to an employee identity.
An avatar on a shared Gibraltar business WhatsApp phone may represent a brand, store or shift operator and cannot be bound automatically to one employee. This article handles account relationships rather than repeating the visitor-phone page.
Define the contact-point type first
| Type | Linked entity | Avatar meaning |
|---|---|---|
| Shared business | Organisation/team | Brand or operating profile |
| Store phone | Location | Store profile |
| Confirmed personal | Person | Still a limited observation |
| Unknown | Conflict queue | No inference |
Business status is not company certification
Account type cannot prove company legitimacy, current employment or control by one person.
Keep avatars out of employee identification
Do not perform face matching or infer name, role, gender, age or shift from an image.
+350 does not prove an organisational relationship
Numbering handles format. Contracts, store records or confirmed business evidence establish affiliation.
Put mapped phones in a relationship graph
Store relationship_type, observed_at and review_state. One-to-many relationships do not overwrite master phones.
TXT carries the contact phone only
Employee lists, roles and schedules are not uploaded. Excel reconnects through batch_row to the organisational contact point.
Do not recheck images for departures and shifts
Internal workforce and account-management processes update employee change. Avatar observation is not proof of employment.
Assign access by organisational role
Sales sees organisational contact state; relationship reviewers handle mappings and temporary images.
The second Gibraltar page’s value
It answers which business contact point a phone belongs to, not where a visitor comes from. Title, slug and body remain independent.
