Contact names across channels

A contact is one person, but every channel has its own idea of what that person is called. Arino One resolves those competing signals into a single canonical display name per contact, so the same customer reads the same way in the inbox, in search and in the CDP — and you can override it by hand when the resolved name isn't the one you want.

The problem

Channels don't agree on names, and most of them aren't trying to:

• WhatsApp passes the profile name the person chose themselves. That might be their full legal name, or "Dad", or a shop name, or an emoji.
• Some channels pass a name only when the user has shared one, or pass nothing beyond an identifier such as a phone number.
• Names arrive at different times. A first message might carry nothing useful; a later one might carry a real name.

Left unresolved, the same customer shows up as three different-looking people. Agents don't recognise a returning contact, search finds one record but not another, and reports count one person twice.

What Arino One does

Rather than storing a name per channel, the instance resolves one display name per contact from the best available inbound signal, and shows that everywhere. When an inbound message carries a better name signal than what's on record, the display name can improve to match.

The rule that matters in practice is simple: a name you set manually wins. Absent a manual name, the best available inbound signal is used.

Override the name

Open the contact and set the name yourself when the resolved one isn't right. Common cases:

• The profile name is a nickname or handle, but you need the account holder's real name.
• You need the name to match a CRM, an invoice or a delivery record.
• The profile name is an emoji, blank, or something you'd rather not display to your team.

A manual name is a deliberate statement that you know better than the channel, and it is treated that way — later inbound signals don't quietly undo it.

Practical notes

• Don't treat a profile name as identity verification. It's self-declared and freely editable by the customer. For anything sensitive, verify properly — see OTP and 2-factor verification.
• Fix the name on the contact, not in the conversation. Renaming once at the contact level is what makes search and segments behave.
• A name is personal data. Whatever the source, it falls under the same retention and privacy posture as the rest of the contact record — see consent and opt-in.

Billing

Name resolution and manual overrides are part of the contact record and included in the flat $50/month instance connection and management fee. There's no extra charge for contacts, resolution or edits. See billing and plans.

Frequently asked