The counterparty card
Before you start a session, the main window has a Contact block — a card for the person you are about to talk to. It is optional: a session starts fine without it. A filled-in card does two things.
What the card gives you
- Sharper prompts. The name and the company go into the prompt context, so Sayply refers to the conversation specifically instead of a generic "the other person says…".
- A recognizable contact in your CRM. Every field of the card travels with the outgoing webhook and into the PDF report. Most CRMs match an existing contact by phone or email — or create a new one — so you do not have to link the call by hand.
Fields
Only the name is visible at first. The + Company, phone, email… button expands the rest: company, phone, email, messenger.
Only the name and the company are used for prompts during the call. Phone, email and messenger are deliberately not sent there: they add nothing to prompt quality, so there is no reason to pass them.
The local contact book
Every session start saves the card into a local book — on your computer, not on a server. Next time, start typing the name and the list will suggest people you already talked to: picking one fills in all the fields at once.
If you pick a contact from the list and then edit the name, Sayply assumes you are looking for a different person and saves a new card instead of overwriting the old one.
Where to next
- What you get after the call — where the card data ends up.
- CRM export — setting up the webhook.