Close more deals,
faster.

Companies, contacts & leads

A proper account record behind every deal, and leads that convert into a contact, a company and a deal in one step instead of three.

• Companies with owners, tags and the custom fields your business actually sells on
• Lead scoring rules you set — the Hot badge says why it says Hot
• Convert a lead into contact + company + deal without retyping
• Duplicate-aware imports, and a workspace-wide search across every record type
• A recycle bin, so a deleted record is a recoverable one

Activities, tasks & the feed

Calls, meetings, emails, tasks and notes land on the record they belong to, next to the history of what changed and who changed it.

• Calls, meetings, emails, tasks and notes, each against a company, contact, lead or deal
• My Tasks — one list across every record you own or are watching
• A merged activity feed per record and per workspace
• Internal chat: a colleague, a named group, or a task’s own discussion thread
• Notifications in the bell, not in your inbox

Modules you define

Fields, sections and whole objects your business needs and nobody else’s — Properties, Shipments, Contracts, Inspections — added in a minute, not in a release.

• A module is a row, not a migration: it never touches another client’s data
• Its own fields, list view, optional Kanban board and record card, generated from the definition
• Every value validated and coerced server-side against its field type
• Link module records to companies, contacts and deals like any built-in object

Email, WhatsApp & SMS on the record

Message a customer from their card or from an automation, and the conversation stays on the record, not on someone’s phone.

• Email from the record card, threaded into the feed
• WhatsApp through TicAte WhatsApp — offered when the workspace has both apps
• SMS through your provider
• Automation rules can send any of them when a stage is reached

How the WhatsApp join works

Client and vendor money, against the dealNew

What a deal earned and what it cost, worked out from whatever is attached to it — so profit on a job is a number you can see, not one somebody assembles in a spreadsheet afterwards.

• Money in — invoices paid and client payments, totalled against the deal
• Money out — vendor bills, subcontractor costs and expense claims, against the same deal
• Any module you build can be marked money in or money out; the deal picks it up automatically
• Committed against paid, so you can see what you still owe as well as what has gone
• Gross profit, net cash and margin per deal, with a breakdown by vendor and by module
• Nothing is stored and later goes stale — every figure is the sum of what is attached right now
• A client-facing role sees the income side and never learns a cost figure existed — the fields are removed, not blanked

Tic Buddy, the assistant in the cornerNew

Ask your CRM a question in plain language and get the answer from your own records — on your own AI key, and inside your own permissions.

• “How many leads came in this week?”, “which deals close this month?” — answered from leads, deals, contacts, companies and tasks
• Bring your own model and key: Anthropic, OpenAI or Google. You pay the provider, and you can switch
• The model never touches the database. It may only ask for data through one read tool, which runs as the person asking
• So the same question gives an admin every record and an agent only theirs — and a module someone may not read comes back as a refusal, never as a number
• Optional: let it do small jobs on request, or keep it read-only
• Mask personal details before anything leaves for the model, if you would rather it never saw names
• Every question, answer and lookup is logged, so you can audit exactly what was asked and what it read
• Switch it off entirely and nothing else in the CRM changes

Campaigns built from the records you already have

Pick an audience with the same filters you use everywhere else, preview exactly who it resolves to, send a test, then send — and the replies come back as conversations rather than a report.

• Email and WhatsApp campaigns, with the audience taken from a CRM filter
• A preview of who it will reach, and a test send, before anything leaves
• Replies arrive in the contact centre as conversations on the record
• Owners, admins and managers only — messaging a thousand customers is not one click away from an agent

Drive, and documents a workflow writes for you

Every file the workspace has in one place — including the ones that arrived through tasks, chats and record fields — and document templates an automation can fill in and file.

• My Drive for yours, Company Drive for everyone’s
• Files that came in through tasks, chats and record fields appear under their own headings
• Document templates a workflow turns into finished files, filed against the record
• Every byte counted once — against the workspace’s plan, and against the person who uploaded it

Your own address, your own schema

Every client gets you.crm.ticate.com — or crm.yourcompany.com — and a database schema of their own. Isolation is the database’s, not a filter in the code.

• Wildcard subdomains out of the box; custom domains verified over DNS
• One database schema per client — a tenant’s connection can only see its own
• Workspace-bound sessions; a ticket minted for one client is useless at another’s address
• Attachments stored per workspace and served through signed links