Skip to main content
Everyone who has written to this assistant. Contacts are not created by hand in the usual case — they appear the moment someone first sends a message.

​
The list

Filters narrow the list, with Apply filters and Reset. In the new console, search matches the Channel user ID, and the Channel and Language filters narrow the list as soon as you pick a value; choose “All” to clear one. The list shows only the people who have written to this assistant’s channels, newest activity first, and can be sorted by when they first wrote.

​
The contact card

Open a contact to see everything stored about them.
  • Identity — channel, channel user ID (with a copy button), language, username, then their tags and groups. In the new console it also shows when the contact first wrote and when they last changed.
  • Profile — the single values a flow has collected, such as a name or a phone number.
  • One section per group of attributes — values a flow stored under a group name, with the number of fields in the heading.
  • From platform — what the messenger itself reported when they first wrote. Closed by default.
Values are shown the way the flow declared them: numbers with separators, dates in your language, yes/no answers as Yes or No. When a contact has more than three attribute groups, the profile and the groups start closed so the page stays scannable. In the new console the keys are also listed alphabetically.

​
Tags and groups

With the Manage contacts permission the card has Manage tags and Manage groups (in the new console, Edit tags and Edit groups). Both replace the whole set: what you save is exactly what the contact has afterwards. A tag set by a flow stays as long as it is in the set you save. Without the permission you can read the card but not change it.

​
Where the details come from

A contact starts as almost nothing: a platform identifier and a channel. That is all a first message carries. Everything else is learned. A name appears once a flow asks for one and stores it. A language is set when the platform reports one or a flow establishes it. Attributes accumulate as conversations collect them.
A list full of numbers and blank names is not a fault. It means those people have written but no flow has yet asked them anything that would fill the columns in. If names matter to you, that is a flow to write rather than a setting to change.

​
One person, several contacts

A contact belongs to a channel. The same human writing on two platforms produces two contacts, and FaPost does not merge them — it has no reliable way to know they are the same person, and guessing wrong would join two strangers’ histories.

​
Language

The contact’s language decides which translation they receive, both in flow content and in broadcasts. When it is unknown, the assistant’s default is used, and failing that the tenant’s fallback — see Settings.

​
Grouping and selecting

Two different tools, easy to confuse:
  • Groups — a list you maintain by hand
  • Segments — a condition, evaluated against everyone
Reach for a group when membership is a decision, and a segment when it is a property.