Standard lead fields and their values

Every lead in Sales Workshop has a set of standard fields. Any of them can be sent to a field of your CRM: Settings → Leads and CRM → Field mapping, with a source from the tables below on the left and your CRM field on the right.

How values are sent

Fields marked «Code» are sent as the code from the table, for example not_reached, untranslated. Codes do not change, so you can build CRM filters, automations and reports on them.
If the CRM field is a list, match each code to a list item right in the mapping row. A code without a matched item is not sent to a list field.
An empty value is not sent and never overwrites what is already on the record.
Sending the same lead again updates the same deal or lead in the CRM instead of creating a new one.

Lead fields

Field	Mapping source	Values
Summary	`lead:summary`	Text. A short summary of the conversation or call, written by the AI.
Situation	`lead:current_situation`	Text. The client's current situation, in the client's words.
Volume	`lead:volume`	Text. Size of the need: quantity, scale, number of guests.
Goals	`lead:goals`	Text. What the client wants to achieve.
Timeline	`lead:timeline`	Text. When the client needs it. Sent to a date field only when it is a date.
Budget	`lead:budget_level`	Text. The budget as the client stated it. Sent to a number field only when it is a number.
Channel	`lead:channel`	Code. Where the lead came from. `phone` — Phone call `telegram` — Telegram `whats_app` — WhatsApp `max` — MAX
Channel type	`lead:channel_type`	Code. `voice` — Voice `text` — Text chat
Call outcome	`lead:call_resolution`	Code. Voice leads only; empty when neither happened. Later calls never clear it. `transferred` — Transferred to a manager during the call `callback_requested` — The client asked to be called back
Call result	`lead:call_result`	Code. The result of the lead's latest call. Voice leads only. `not_reached` — Not reached: no answer, busy, dialing error `robot` — Voicemail or a robot answered `no_conversation` — Answered, but the client said nothing `dropped` — A person picked up, said hello and would not talk `wrong_number` — The person said it is the wrong number `refused` — Refused `callback_requested` — Asked to be called back `no_agreement` — Talked, nothing agreed `agreed` — The lead was handed to a manager `transferred` — Transferred to a manager during the call
Direction	`lead:direction`	Code. Who started the conversation the lead came from. Set once and never changed. Call result is written for both inbound and outbound calls, so check direction here. `inbound` — Inbound: the client called or wrote in `outbound` — Outbound: we called or wrote first (campaign, CRM-triggered call)

When a lead reaches the CRM

By default, a lead goes to the CRM when it is handed to a manager. For a voice agent you can choose «Every call» under «What goes to the CRM» (agent → «Playbook» tab → «Lead handoff»). Then every call goes to the CRM, unreached numbers included, with the outcome in lead:call_result. Such leads do not count as deals in Sales Workshop statistics.

Contact fields

Field	Mapping source	Values
First name	`contact:first_name`	Text.
Last name	`contact:last_name`	Text.
Phone	`contact:phone`	The number the client called from or the agent dialed.
Callback phone	`contact:callback_phone`	The number the client gave for contact, when it differs.
Company	`contact:company`	Text.
Industry	`contact:industry`	Text.
Role	`contact:role`	Code. The contact's role in their company. `decision_maker` — Decision maker `influencer` — Influencer `executor` — Executor `unknown` — Not established

Custom fields

Besides the standard fields, an organization can add its own: event format, venue, budget, dates. The agent collects them in the conversation; in the mapping they appear as attr:<key> sources. The organization defines their set and values.