—PRODUCT

Leads, customers & records

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.

Ready Plan: all plans

—SUMMARY

What is it for?

Turns names, phone numbers, needs and budgets from conversations into customer records and CRM entries.

01HOW IT WORKS

Three steps to a working result.

Each step is one screen in the panel; nothing goes live without confirmation.

  1. 1 Define the fields

    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.

  2. 2 Collect in conversation

    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.

  3. 3 Review and sync

    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

Real work in one flow.

The three capabilities below are today’s scope; the sample screen is fictional and contains no real customer data.

01

Customer ledger

Four summaries, tags, bulk actions, archive and two-step permanent delete in one list; archiving is not deleting.

  • Customer
  • List
  • Tag
02

Structured records

Records are built from schema fields; COMPLETE/MISSING status and sensitive-field privacy are preserved.

  • Record
  • Privacy
  • Schema
03

CRM and lead notification

One-way sync to five CRMs or a signed lead notification; no transcript, audio or summary goes to the CRM.

  • CRM
  • Notification
  • Transcript
SAMPLE SCREEN · FICTIONAL Customers · last 30 days
Total leads 1,284
With phone 1,102
With email 684
Added this month 186
Sample row Ada Y. · +90 5** *** ** 42 · WhatsApp · Tag: Quote

Sample screen; the name and number are fictional and contain no real customer data.

03THE DIFFERENCE IS IN THE DETAILS

Small details that change the decision.

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.

01

Customers

The customer ledger built from contact details captured in conversations.

12 items
01

No separate Lead table

A lead is a conversation where contact details were shared; one of name, email or phone is enough, a company name alone is not.

  • Email
  • Conversation
  • Phone
02

Four summaries

Total leads, with phone, with email and added this month are shown at the top.

  • Email
  • Phone
03

Table columns

Name, company, phone, email, channel type, status, tag, message and last contact are listed.

  • Email
  • List
  • Message
04

Tags

Tags are business-specific, take a tone from a preset palette, require at least two characters and reject duplicate names.

  • Tag
  • Character
05

Bulk actions

Tagging, CSV download and “Remove from list” run in bulk; changing the filter clears the selection.

  • CSV
  • Filter
  • List
06

Archive does not delete

“Remove from list” archives the record, it does not delete it; archived records are hidden by default and shown with “Show archived”.

  • Archive
  • Delete
  • List
07

Restore always opens

Restoring from the archive always sets OPEN; the previous RESOLVED status does not return.

  • Archive
  • Status
08

Two-step permanent delete

First a confirmation that states the consequences, then typing “PERMANENTLY DELETE”; messages and attachments are deleted, billing counters do not change.

  • Delete
  • Approval
  • Message
09

CSV in the browser, with BOM

CSV is produced in the browser; with a selection only selected rows are included, and a BOM is added for Excel.

  • CSV
  • Assistant
10

Starts with forty records

Pagination starts with 40 records and continues with “Load more (N left)”.

  • Record
  • Assistant
11

Phone/email are not masked

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.

  • Privacy
  • Email
  • Hidden
12

Honest message on load failure

If detail messages cannot load, no error is shown; it says “No messages recorded in this conversation”.

  • Message
  • Conversation
  • Record
02

Records

The table and CSV of structured fields collected in conversations.

6 items
01

Only filled records

Only conversations whose metadata.data field is non-empty become rows.

  • Record
  • Conversation
  • Field
02

COMPLETE/MISSING

If one required and non-sensitive field is empty the record is MISSING; a missing sensitive field does not make it MISSING.

  • Privacy
  • Field
  • Record
03

Sensitive field hidden

Columns come from fields with reportShow and without sensitive; a sensitive field value never appears in the table or CSV.

  • Privacy
  • Field
  • Hidden
04

Search on visible fields

Search runs on customer name, channel and visible field values.

  • Field
  • Search
  • Customer
05

CSV file name

The CSV file name is records-YYYY-MM-DD.csv.

  • CSV
  • File
  • Record
06

Per-agent schema is not read

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.

  • Schema
  • Sector
  • Field
03

Data to collect

The schema that decides which field the assistant asks for, how and from whom.

11 items
01

Eight field types

The types are text, number, choice, phone, email, address, date and yes/no.

  • Field
  • Email
  • Number
02

New field defaults

A new field opens as text named “New field”; askAI, showInForm and showInReport are on.

  • Field
  • Report
03

Sensitive fields close automatically

When marked sensitive (privacy law art. 6), askAI and showInForm turn off and cannot be reopened; the assistant/widget never collects the field.

  • Privacy
  • Field
  • Closing
04

Server rejects sensitive fields

The server never accepts a sensitive field and produces no error, so its existence does not leak.

  • Privacy
  • Field
  • Server
05

Duplicate keys rejected

Using the same key twice raises “The same key is used more than once”; empty keys are silently skipped.

  • Duplicate key
  • Assistant
06

Key and text limits

The key is at most 64, text 200, address 500 and email 254 characters.

  • Limit
  • Email
  • Character
07

Schema precedence

The active schema order is Assistant settings > business settings > sector default; the panel edits only the business schema.

  • Schema
  • Order
  • Sector
08

Fill only empty values

An existing filled value is not overwritten; repeated information is idempotent.

  • Value
  • Assistant
09

One question per message

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.

  • Message
  • Question
  • Privacy
10

No phone question on voice

The phone is not asked on the voice channel; the caller number comes from the channel.

  • Voice
  • Question
  • Phone
11

Sector reset does not restore customisations

“Return to sector default” does not restore customisations; it loads only the default schema.

  • Sector
  • Schema
04

CRM, lead notification and settings

One-way CRM sync, signed notification and business settings that carry the lead outward.

12 items
01

Settings card order

Organisation details → end-of-conversation email → lead notification → CRM sync → SMS provider → read-only details → subscription link.

  • Order
  • Settings
  • CRM
02

Organisation editing

Name at least two characters, time zone in Europe/Istanbul form, language TR/EN; plan, payment and status do not change here.

  • Character
  • Plan
  • Language
03

Short name is immutable

The short name is immutable; the details card shows name, short name, status, plan, language, time zone and signup date read-only.

  • Short name
  • Plan
  • Language
04

Write permission

Only owners/admins write settings; members get 403. Settings are merged, and an empty secret key keeps the existing secret.

  • Permission
  • Settings
05

Reserved settings are closed

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.

  • Settings
  • Closing
  • Price
06

End-of-conversation email

Multiple recipients are entered with commas, semicolons or lines; addresses are lower-cased, de-duplicated and invalid ones are shown before saving.

  • Email
  • Conversation
  • Keyboard
07

Lead notification

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.

  • Notification
  • Shipping
  • Character
08

One-way CRM

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.

  • CRM
  • Record
  • Test
09

CRM duplicate behaviour

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.

  • CRM
  • Email
  • Record
10

CRM privacy boundary

Only name, phone, email, company, channel and conversation ID go to the CRM; no transcript, audio or summary.

  • CRM
  • Privacy
  • Email
11

Three SMS types

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.

  • SMS
  • Approval
  • Password
12

SMS İYS boundary

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.

  • SMS
  • Handover
  • Customer

04CONTROL AND SECURITY

Human approval, masking, records.

These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.

Sensitive fields are not collected

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.

Two-step permanent delete

Permanent delete first requires a confirmation that states the consequences, then typing “PERMANENTLY DELETE”; messages and attachments are deleted, billing counters do not change.

No transcript to CRM

CRM sync carries only name, phone, email, company, channel and conversation ID; transcript, audio and summary stay out.

05WHICH PLAN

Plan and add-ons.

Customers, records and CRM sync are available on every plan with no separate gate. Write access is limited to OWNER/ADMIN.

Starter ₺2,750 / mo excl. VAT This surface is on every plan
Growth ₺7,900 / mo excl. VAT This surface is on every plan
Business ₺17,500 / mo excl. VAT This surface is on every plan

All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →

06FAQ

Four questions, four clear answers.

Is there a separate lead table?
No. A lead is a conversation where contact details were shared; one of name, email or phone is enough. There is no separate Lead model.
Will CSV break in Excel?
CSV is produced in the browser with a BOM for Excel. With a selection only selected rows are downloaded; the file name is records-YYYY-MM-DD.csv.
Can permanent delete be undone?
No. Two-step permanent delete removes messages and attachments; billing counters do not change. Archiving does not delete and can be undone.
What goes to the CRM?
Only name, phone, email, company, channel and conversation ID. No transcript, recording or summary goes to the CRM. Sync is one-way.

+RELATED POSTS

Posts on this topic

Posts from the same topic cluster that complete this page. Leads & records posts.

Guide

What is an AI customer agent?

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.

Let’s set this up on your account.

Try free for 14 days without a credit card; we will do the first setup together.

Call Start 14-day trial