Customer ledger
Four summaries, tags, bulk actions, archive and two-step permanent delete in one list; archiving is not deleting.
- Customer
- List
- Tag
—PRODUCT
Keep contact details, structured records and CRM sync from conversations in one place.
A visitor who shares a name, phone or email in a conversation enters the customer list; there is no separate Lead table. The Records screen shows structured fields collected under the data schema; a sensitive field value never appears in the table or CSV. The same data can sync one-way to a CRM or leave via a signed lead notification.
—SUMMARY
Turns names, phone numbers, needs and budgets from conversations into customer records and CRM entries.
01HOW IT WORKS
Each step is one screen in the panel; nothing goes live without confirmation.
On the data-to-collect screen choose one of eight field types; the key is at most 64 characters. If a field is marked sensitive, the assistant and widget never ask for it again.
The assistant asks one question per message, does not repeat known values and fills only empty fields. It does not ask for a phone on the voice channel; the caller number comes from the channel.
Filter on the Customers and Records screens, download CSV or enable CRM/lead notification sync. CSV is produced with a BOM for Excel.
02WHAT IT DOES
The three capabilities below are today’s scope; the sample screen is fictional and contains no real customer data.
Four summaries, tags, bulk actions, archive and two-step permanent delete in one list; archiving is not deleting.
Records are built from schema fields; COMPLETE/MISSING status and sensitive-field privacy are preserved.
One-way sync to five CRMs or a signed lead notification; no transcript, audio or summary goes to the CRM.
Sample screen; the name and number are fictional and contain no real customer data.
03THE DIFFERENCE IS IN THE DETAILS
41 items, each tied to a rule, setting or automatic behaviour in today’s product. No unsupported number, ratio or promise appears in this list.
The customer ledger built from contact details captured in conversations.
A lead is a conversation where contact details were shared; one of name, email or phone is enough, a company name alone is not.
Total leads, with phone, with email and added this month are shown at the top.
Name, company, phone, email, channel type, status, tag, message and last contact are listed.
Tags are business-specific, take a tone from a preset palette, require at least two characters and reject duplicate names.
Tagging, CSV download and “Remove from list” run in bulk; changing the filter clears the selection.
“Remove from list” archives the record, it does not delete it; archived records are hidden by default and shown with “Show archived”.
Restoring from the archive always sets OPEN; the previous RESOLVED status does not return.
First a confirmation that states the consequences, then typing “PERMANENTLY DELETE”; messages and attachments are deleted, billing counters do not change.
CSV is produced in the browser; with a selection only selected rows are included, and a BOM is added for Excel.
Pagination starts with 40 records and continues with “Load more (N left)”.
Phone and email are not masked in the table or CSV; the masking used for comments does not apply here. This is a deliberate choice and requires the business’s own privacy assessment.
If detail messages cannot load, no error is shown; it says “No messages recorded in this conversation”.
The table and CSV of structured fields collected in conversations.
Only conversations whose metadata.data field is non-empty become rows.
If one required and non-sensitive field is empty the record is MISSING; a missing sensitive field does not make it MISSING.
Columns come from fields with reportShow and without sensitive; a sensitive field value never appears in the table or CSV.
Search runs on customer name, channel and visible field values.
The CSV file name is records-YYYY-MM-DD.csv.
Table columns come from the business/sector schema; a per-agent data schema is not read on this screen, so those fields do not appear.
The schema that decides which field the assistant asks for, how and from whom.
The types are text, number, choice, phone, email, address, date and yes/no.
A new field opens as text named “New field”; askAI, showInForm and showInReport are on.
When marked sensitive (privacy law art. 6), askAI and showInForm turn off and cannot be reopened; the assistant/widget never collects the field.
The server never accepts a sensitive field and produces no error, so its existence does not leak.
Using the same key twice raises “The same key is used more than once”; empty keys are silently skipped.
The key is at most 64, text 200, address 500 and email 254 characters.
The active schema order is Assistant settings > business settings > sector default; the panel edits only the business schema.
An existing filled value is not overwritten; repeated information is idempotent.
The assistant asks one question per message, does not repeat what it knows, does not ask sensitive fields and calls save when it learns something.
The phone is not asked on the voice channel; the caller number comes from the channel.
“Return to sector default” does not restore customisations; it loads only the default schema.
One-way CRM sync, signed notification and business settings that carry the lead outward.
Organisation details → end-of-conversation email → lead notification → CRM sync → SMS provider → read-only details → subscription link.
Name at least two characters, time zone in Europe/Istanbul form, language TR/EN; plan, payment and status do not change here.
The short name is immutable; the details card shows name, short name, status, plan, language, time zone and signup date read-only.
Only owners/admins write settings; members get 403. Settings are merged, and an empty secret key keeps the existing secret.
Reserved settings such as add-ons, internal account, legal consents, erasure, white label, discount table, pricing and outbound are closed to the business; the request is rejected.
Multiple recipients are entered with commas, semicolons or lines; addresses are lower-cased, de-duplicated and invalid ones are shown before saving.
An http(s) address and a secret key of at least 16 characters are required; event, delivery ID and signature travel in headers. The key is shown only when generated; a test delivery and last health are visible.
Paraşüt, HubSpot, Bitrix24, Pipedrive and Kommo receive one-way sync; credentials are encrypted and never returned to the panel. A test opens no record, only a ping.
HubSpot does not open a new record on an email match; in Paraşüt every lead is a new person; Bitrix24, Pipedrive and Kommo search by phone/email.
Only name, phone, email, company, channel and conversation ID go to the CRM; no transcript, audio or summary.
NetGSM (user code + API password + approved header), sms.to (Bearer) and generic HTTP are supported; credentials are encrypted and leaving them blank keeps the current value.
Handover SMS is treated as operational and goes with iysfilter=0; commercial-message consent stays with the customer. Without a provider the last step is not sent.
04CONTROL AND SECURITY
These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.
When a field is marked sensitive the assistant/widget does not ask; the value is not shown in the table or CSV and is entered only by an authorised panel user.
Permanent delete first requires a confirmation that states the consequences, then typing “PERMANENTLY DELETE”; messages and attachments are deleted, billing counters do not change.
CRM sync carries only name, phone, email, company, channel and conversation ID; transcript, audio and summary stay out.
05WHICH PLAN
Customers, records and CRM sync are available on every plan with no separate gate. Write access is limited to OWNER/ADMIN.
All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →
06FAQ
+RELATED POSTS
Posts from the same topic cluster that complete this page. Leads & records posts.
What WhatsApp Business API is, how it differs from the WhatsApp Business app, how to set it up, and how conversation-based pricing works.
A plain guide to what an AI customer agent does, how it answers from a knowledge base and when it hands a conversation to a person.
When two people share one number, questions get lost; when one person runs it, they pile up on a day off. A guide to which WhatsApp auto-reply tool solves what, and where to stop.
Try free for 14 days without a credit card; we will do the first setup together.