Manage contacts, fields, and sales pipelines

Keep customer records useful

1. Open Customers.
2. Review identity, contact details, channels, tags, fields, notes, conversations, appointments and deals.
3. Correct or merge duplicates when the same customer appears more than once.

• Use tags for flexible markers: VIP, callback requested or campaign source.
• City is a standard contact field for every industry. Set it in Add Contact or the contact details; search, import and export it as City. Existing contact City custom-field values move into this field, and the duplicate custom field is removed. Order delivery cities and preferred-city fields stay separate.
• The contacts table shows City. Company and Country remain in contact details and exports, but have no table columns.
• Use custom fields for other structured facts, such as service or renewal date.
• Keep a field only when it supports a decision, automation, assignment or report. Prefer controlled choices when possible.

Manage deals

1. Open Pipelines and define stages that reflect real buyer progress.
2. Create or update the deal from the customer context when a conversation becomes an opportunity.
3. Set an owner, known value, next action and expected timing.
4. Move stages when evidence changes. Keep pricing exceptions and commitments with the responsible salesperson.

On mobile, swipe the board to see more stages. To move a card, press and hold briefly, then drag it to the destination stage. Tap a card to open it.

Use Summary period for date presets or a custom start/end date. It filters the summary metrics only; the Kanban board and stage totals include all dates. Expand More metrics for the remaining calculations. Search opens Table to search all leads, including records not loaded on the board. Use Manage Pipelines for stage settings; Add Pipeline is in the pipeline selector menu.

Automations can handle predictable updates and reminders.

Import waiting?

Imports and broadcasts share background processing capacity. Saved progress is retained while a batch waits; avoid uploading the same file again. This does not deliberately delay interactive AI requests.