Read a customer profile
One contact on one chatbot: contact fields, lead status, lifecycle stage, attribution, consent, and a dated activity timeline.
Browse topics
What it is
A customer profile is everything Agentency knows about one contact on one chatbot, on a single page: their contact details, where they came from, what consent they gave, and a dated list of everything that has happened to them.
It is also where you work the lead. Lead status and lifecycle stage are editable here, and so are the contact fields themselves if a visitor mistyped something.
When you would use it
Before you reply to someone, so you know what they already asked. When a teammate forwards you a chat and you need context. When you are moving a lead along your pipeline. Or when someone asks you to prove what data you hold about them and where it came from.
Where to find it
Open Dashboard → Customers and select any row.
Steps
- Open Dashboard → Customers and click the person.
- Read the Profile section: name, email, phone, company, job title, website, country, and any extra fields your form collects. Only fields you actually asked for will have values.
- Note which chatbot the record belongs to. The same person on another chatbot is a separate record.
- Set Lead status as you work them: New, Contacted, Qualified, Unqualified, Converted, or Blocked.
- Check Lifecycle stage — Visitor, Lead, Customer, or VIP. It starts moving on its own and you can override it.
- Read Source & attribution to see how they arrived: the source, the pages they landed on and left from, the referring site, and any campaign parameters that came with the link.
- Read Consent & privacy to see what they agreed to and when.
- Scroll the Activity timeline for the dated history.
- Save your edits. There is no separate publish step.
What you will see
The page is organised into four blocks — Profile, Source & attribution, Consent & privacy, and Activity timeline — plus the conversation count and a way through to the transcripts.
Anonymize also lives on this page, as a clearly marked destructive action. It is not the same as delete, and it cannot be undone. Read Anonymize a customer before you use it.
Lead status versus lifecycle stage
Two similar-looking fields that answer different questions, which is why both exist:
- Lead status is your sales process: has anyone contacted this person, are they qualified, did they buy. Nothing sets it for you. It is manual, and it drives the Converted and Conversion rate tiles on the list.
- Lifecycle stage is what kind of contact this is: an unknown visitor, a lead with contact details, a paying customer, a VIP. It begins automatically — a record with neither an email nor a phone starts as a visitor and is promoted to a lead the moment either arrives — and you take over from there.
Use lead status for pipeline reporting and lifecycle stage for segmentation. Changing either is a note to your own team; it never emails the person and never triggers anything.
Reading the activity timeline
The timeline is append-only, oldest at the bottom, and includes actions taken by your own team as well as the visitor's. The entries you will see:
| Entry | What happened |
|---|---|
| Lead form started | They began filling in the form |
| Lead form submitted | They completed it |
| Lead form skipped | They chose to skip it, where skipping is allowed |
| Lead form validation failed | A submission was rejected — a malformed email, usually |
| Chat blocked pending lead | They tried to chat before completing a required form |
| Customer created / Customer updated | The record was created, or new details filled gaps in it |
| Conversation linked | A conversation was attached to this person |
| Customer viewed | Someone on your team opened this profile |
| Customer exported | This person was included in a CSV export |
| Customer anonymized / Customer deleted | The destructive actions, recorded permanently |
Two things worth knowing about it:
- The timeline records field names, never field values. A validation-failure entry tells you which field was rejected, not what the visitor typed.
- Your team's own actions are logged too. Viewing a profile and exporting a list both leave an entry. That is deliberate — if you ever have to answer "who looked at this person's data", the answer is here.
Lead form started is only recorded when someone actually attempts a submission, so it undercounts. A visitor who opens the form and wanders off leaves no trace.
Editing contact details
You can correct the fields directly. Two behaviours to be aware of:
- New submissions fill gaps, they do not overwrite. If a record already has a name and the visitor submits a different one later, the original stays. This protects a good value from being clobbered by a careless second entry — but it also means an out-of-date value will not fix itself. Edit it here.
- Email and phone are how Agentency recognises a returning visitor. Changing them changes who future conversations get attached to. Correct a typo by all means; do not repurpose one record for a different person.
Limits and plan notes
Editing requires the manage-customers permission. A member with view-only access can read the profile but not change anything, export, or anonymize. See Roles and permissions.
There is no merge action. If you have duplicate records for one human — usually because they used two chatbots, or an email on one visit and a phone on another — they stay separate. Deduplicate in your own system after an export.
Phone numbers only match reliably in international format. A number typed without a country code is stored and shown, but it will not be used to recognise the same person on their next visit.
There is no email button. Agentency does not send messages to your contacts. Copy the address into whatever you normally use.
Common problems
I cannot edit anything.
Either your role is view-only, or you have followed a link into a workspace you are not currently in. Check the account switcher first, then your permissions.
The name is a random-looking string.
Your website passed a visitor identifier without a display name, and no form has been completed. Add a name field to the form, or pass a proper display name with the widget's visitor identity — see Widget visitor identity.
Company is empty for everyone.
Only what you ask for gets collected. Add the company field on Chatbots → your chatbot → Settings → Customer data, and it will start filling on new submissions. It will not fill retrospectively.
Their conversations are not showing.
Conversations link to a person when a form or a Call action ties them together. Chats from before they identified themselves stay anonymous. Look for them under Conversations instead.
I set them to Converted and nothing happened.
Correct. Lead status is a label for your team. It moves the Converted and Conversion rate tiles on the Customers list, and nothing else.
Common questions
What is the difference between lead status and lifecycle stage?
Lead status is your sales process and is entirely manual. Lifecycle stage is what kind of contact this is, and it starts moving on its own — a record is promoted from visitor to lead as soon as an email or phone arrives.
Does changing someone's status email them?
No. Agentency never messages your contacts. Status is a label for your team, and it only feeds the Converted and Conversion rate tiles on the list.
A visitor submitted a corrected name and the old one is still showing.
New submissions fill gaps rather than overwrite, so a value that is already there is protected from being clobbered. Edit the field by hand to correct it.
Is it recorded when my team opens a profile?
Yes. Viewing a profile and exporting a list both leave an entry on the timeline, so you can always answer who looked at someone's data.
Why are their older conversations not attached?
Conversations link to a person at the point the form or Call action identifies them. Anything from before that stays anonymous and lives under Conversations instead.
Was this article helpful?
Related articles
Open the customers list
Dashboard → Customers is the contact list your chatbots build. Search, filter by chatbot and status, and read the four tiles correctly.
Anonymize a customer
Permanently strip a person's identity from your workspace, including their chat text. Irreversible, and the right tool for an erasure request.
Set lead capture fields
Choose what your chatbot asks for before its first reply, under Settings → Customer data. Off until you switch it on.
Where leads come from
Three sources create a customer: the widget or hosted page, the dashboard, and Call actions. Anonymous chatting creates nothing.
Ready to try it on your own content?
Create a free workspace, add a document, and ask the questions your team is tired of answering.