Documentation

Everything you need to get the most out of Kordic CRM — from working your pipeline to connecting your favourite tools.

Getting Started

Using the app

Kordic brings your entire sales workflow into one place. Here's a tour of the core areas you'll use every day.

Pipeline & stages

Drag and drop leads across custom stages on the Kanban board. Each card shows deal value, owner, and a stale-lead day counter so nothing goes cold.

Leads

Open any lead to see contact details, notes, emails, documents, payments and integration tabs — the full history of the deal in one timeline.

Accounts & Contacts

Manage companies as Accounts, each with multiple Contacts. Pick an account when adding a deal and its contacts auto-fill instantly.

Payments

Record payments with VAT, track outstanding balances, and route them through the accountant confirmation workflow for a clean audit trail.

Analytics

See your pipeline funnel, win rates, revenue trends and per-user performance rankings — updated in real time.

Team & roles

Invite Owners, Managers, Agents and Accountants. Role-based access controls exactly what each person can see and do.

Documents

Upload contracts, proposals and invoices per lead, or save Google Drive links. Download anytime via secure presigned URLs.

AI pre-call briefings

Before each call, get a 3-part AI summary — situation, talking points, and risk flags — powered by Claude. Available on Growth & Business plans.

Integrations

Connect your tools

Bring meetings, email and messaging into Kordic so every interaction is logged alongside the deal. Below are step-by-step guides for adding, using and removing each integration.

Zoom

Schedule Zoom meetings from a lead and pull meeting transcripts back in as notes — all without leaving the CRM.

Adding the app

Click the Zoom tab inside the lead, then click Connect Zoom.

You'll be redirected to Zoom's OAuth page. Review the requested permissions and click Allow.

You'll return to Kordic with Zoom showing as Connected.

Troubleshooting

If connection fails, click Disconnect then Connect again.
Make sure you're logged into the correct Zoom account before authorising.
Ensure your browser allows redirects from kordic.io.

Usage

Schedule a meeting

Zoom connectedLead open

Open a lead → click the Zoom tab → + Schedule Meeting.
Fill in the topic, date, time and duration, then click Create.
The join link and details appear in the lead's Zoom tab.

Fetch a meeting transcript

Paid Zoom accountCloud recording enabledMeeting completed

Open the lead → Zoom tab → find the completed meeting → click Transcript.
The transcript is saved as a note on the lead record.

Removing the app

Open any lead → click the Zoom tab → click Disconnect.

You can also revoke access from Zoom under App Marketplace → Manage → Installed Apps.

Data deletion on disconnect

All stored OAuth tokens (access & refresh) are permanently deleted from our database immediately.
Kordic can no longer access your Zoom account.
Previously saved meeting records and transcripts remain in lead notes as historical data — remove them manually if you wish.

Gmail

Send emails and view full conversation history per lead. Every message is logged automatically on the lead's timeline.

Adding the app

Click Connect Gmail, sign in with your Google account and click Allow.

Your Gmail is connected — email history now appears in lead records.

Usage

View email history

Gmail connected

See all emails exchanged with a lead's contact directly inside the lead record — no switching to Gmail.

Send emails

Gmail connected

Send emails to leads from Kordic. Sent emails are automatically linked to the lead record.

Removing the app

Open a lead → Emails tab → click Disconnect Gmail.

Data on disconnect

OAuth tokens are permanently deleted immediately upon disconnection.
Kordic will no longer access your Gmail account.

Outlook

Connect Microsoft Outlook to send emails and keep full conversation history attached to each lead.

Adding the app

Click Connect Outlook, sign in with your Microsoft account and click Accept.

Outlook is connected — email history now appears in lead records.

Usage

View email history

Outlook connected

See all emails exchanged with a lead's contact inside the lead record — no switching to Outlook.

Send emails

Outlook connected

Send emails to leads from Kordic. Sent emails are automatically linked to the lead record.

Removing the app

Open a lead → Emails tab → click Disconnect Outlook.

Data on disconnect

OAuth tokens are permanently deleted immediately upon disconnection.
Kordic will no longer access your Outlook account.

Mailchimp

Sync leads to a Mailchimp audience, run campaigns, and see subscriber status and email activity right on the lead.

Adding the app

As an Owner or Manager, open Workspace settings in Kordic.

Find the Mailchimp section and click Connect Mailchimp, then authorise on Mailchimp's OAuth page.

Back in Kordic, choose the audience (list) you want leads synced to.

Mailchimp shows as Connected and a Mailchimp tab appears on every lead.

Usage

Sync a lead & track activity

Mailchimp connectedAudience selectedLead has an email

Open a lead → Mailchimp tab → click Sync to Mailchimp to add the contact to your audience.
The tab shows subscriber status (subscribed, unsubscribed, cleaned, pending) and the selected audience.
Email activity and real-time events (opens, campaigns sent, unsubscribes) appear as they happen via webhooks.
Managers can click Unsubscribe to remove a contact from the audience.

Removing the app

Open Workspace settings → Mailchimp and click Disconnect.

Data on disconnect

OAuth tokens are permanently deleted from our database immediately.
Kordic will no longer access your Mailchimp account or sync new leads.
Contacts already in your Mailchimp audience remain there — manage them from Mailchimp directly.

WhatsApp Business

All plans

Send and receive WhatsApp messages directly from any lead profile via the WhatsApp Business API. Incoming messages are matched to leads by phone number, and your whole team works from one place — no one needs the WhatsApp Business app.

Prerequisites

🏢 Meta Business Account 📱 WhatsApp Business number 🔑 Owner or Manager role

Adding the app

Create a Meta Business Account — at business.facebook.com, sign in with Facebook, click Create Account and verify your email. Already have one? Skip ahead.

Prepare your number — Kordic's wizard creates your WhatsApp Business Account (WABA) automatically. Just ensure your Meta Business Account is active and you can receive a verification SMS or call.

Connect inside Kordic — open any lead → WhatsApp tab → Connect WhatsApp Business. A Meta pop-up opens; log in with the Facebook account linked to your Meta Business Account.

Scan the QR code — on your phone open WhatsApp Business → ⋮ → Linked devices → Link a device → scan the on-screen code.

You're live — Kordic activates the connection automatically. All agents and managers can now message from any lead's WhatsApp tab.

Troubleshooting

"Facebook SDK not loaded" — wait 5–10 seconds and retry; check your browser isn't blocking Facebook scripts.
Verification code not arriving — make sure the number isn't already active on WhatsApp; try the voice-call option.
Shows disconnected after setup — refresh the page; if it persists, disconnect and reconnect.
Pop-up blocked — allow pop-ups for Kordic, then try again.

Usage

WhatsApp connected

Open a lead → WhatsApp tab to send and receive messages.
Full conversation history is kept per lead, in one place.
Incoming messages are automatically matched to leads by phone number.

Removing the app

Open a lead → WhatsApp tab → click Disconnect (Owner/Manager only).

Data on disconnect

Stored access tokens are permanently deleted from our database immediately.
Kordic will no longer send or receive WhatsApp messages on your behalf.
Previously logged conversations remain on the lead as historical data.

Twilio Calling

Business plan

Call your leads with one click, right from the CRM. Every call is saved on the lead's timeline, and you can optionally record and transcribe calls. You use your own Twilio account and pay Twilio directly — Kordic adds no markup.

🔑 Owner or Manager role (to set up) ☎️ A Twilio account

What you get

One-click dialing — call any lead without leaving Kordic or copying numbers.
Automatic call log — every call is saved on the lead with its time, duration and outcome.
Optional recording — turn it on with one click and a consent tick.
Optional AI transcripts — see a written transcript under each recorded call.
Smarter AI Briefing — call outcomes and transcripts help the Briefing prep your next call.
Use numbers you own — already have Twilio numbers? Link them in one click.

Step 1 — Connect your Twilio account

Open any lead and click the Voice tab.

In the Twilio Console, create a new Standard API Key (name it "Kordic CRM") and copy the Secret right away — Twilio shows it only once.

Back in Kordic, paste your Account SID (starts with AC…), API Key SID (starts with SK…) and the Secret, then click Connect Twilio.

That's it — Kordic checks the details with Twilio and gets the dialer ready. Next, add a phone number.

Tip

Use a Standard API Key — it gives Kordic exactly what it needs to place calls, nothing more.
If you miss copying the Secret, just delete that key in Twilio and create a new one.

Step 2 — Get a phone number

Buy a number through Kordic

Voice tab → Phone numbers → Buy a number.

Pick a country (e.g. US, AE, GB), optionally filter by area code or digits, then click Search.

Tick Set as workspace default if it's your first number, then click Buy. Twilio charges you at its normal rate.

Already own a number?

Numbers in your Twilio account show up under Not linked — click Link to Kordic to use one. Same number, no re-buying.
For linked numbers you can Set default (the caller ID Kordic uses) or Release them back to Twilio.

Step 3 — Make a call

Open a lead that has a phone number and click the green 📞 Call button. (It only shows when the lead has a number.)

The dialer opens with the lead's name. Pick which number to call from if you like, then press the green button.

The first time, your browser asks to use the microphone — click Allow.

During a call you have a timer, a Mute button, and a red End button.
Minimise shrinks the dialer to a small pill so you can keep working while you talk.

Recording & transcripts (optional)

Recording — in the Voice tab, turn on Record calls and accept the consent message. Choose how long recordings are kept (30 / 60 / 90 days, or keep them until you delete them). This only affects future calls.
Transcripts — turn on Twilio Voice Intelligence in your Twilio console, then click Refresh setup in Kordic. New recorded calls then get a written transcript automatically.
You can record calls without transcripts — transcripts are just an extra add-on.

After the call

Open the lead → Notes tab to see the call with its outcome (Completed, No answer, Busy, Canceled, Failed), duration and the numbers used.
If recording is on, click Play recording to listen right there.
If transcripts are on, click Show transcript a minute or so after the call to read it.
The AI Briefing tab uses recent calls to help prep your next conversation.

Who can do what

Owners & Managers — set up Twilio, manage numbers and recording, call any lead, and delete call records.
Agents — call and play recordings for leads they own or are assigned to.
Accountants — can see calls in the feed but can't make calls or play recordings.

Costs

Kordic charges no markup — you only pay Twilio for minutes, number rental, recording storage, and (if used) transcripts.
The Buy Number screen shows an estimated monthly cost; your Twilio invoice is the final word.

Removing Twilio

Voice tab → Disconnect Twilio (Owner/Manager only).

What happens on disconnect

Your Twilio details are removed from Kordic right away.
Your phone numbers stay in your Twilio account — reconnect any time and they're ready to re-link.
Calls already logged stay on the lead as history.

Public API

REST · v1

Read and write your CRM data from anywhere — your website forms, automation tools (Zapier, Make), a data warehouse or a custom integration. Authenticate with an API key you generate yourself; every key is scoped to a single workspace.

🔑 Owner or Manager role 🌐 Base URL: https://api.kordic.io/api/v1

Creating an API key

Click Create key, give it a name (e.g. Zapier production), and tick the scopes it should have (read/write per resource).

Copy the key immediately — it's shown only once and cannot be retrieved again. It looks like kdc_live_….

Keep keys server-side

An API key is a full credential to your workspace — never embed it in a browser app, mobile app, or public repository.
If a key leaks, revoke it from the Developer page — it stops working within about a minute.

Authentication

Send the key as a bearer token (the X-API-Key header is also accepted). Use GET /me to verify a key and see its scopes:

# Verify your key
curl https://api.kordic.io/api/v1/me \
  -H "Authorization: Bearer kdc_live_your_key_here"

# → { "data": { "workspace_id": "…", "scopes": ["leads:read", "leads:write"] } }

Scopes

A key only works on endpoints its scopes allow — read endpoints need :read, writes need :write. A request missing the scope returns 403 permission_error.

leads · contacts · accounts · stages · payments · documents — each has :read and :write
notes:write — log notes/activities onto a lead (read them via the activity timeline)
activity:read — a lead's unified activity timeline

Conventions

All responses are JSON. A single resource comes back as { "data": { … } }; lists as { "data": [ … ], "meta": { … } } paginated with ?page= (default 1) and ?per_page= (default 20, max 100). Errors use a typed envelope.

# Pagination meta (on list responses)
"meta": { "page": 1, "per_page": 20, "total": 137, "total_pages": 7 }

# Error envelope — type is one of:
# authentication_error · permission_error · invalid_request_error · not_found_error · rate_limit_error · api_error
{ "error": { "type": "invalid_request_error", "code": "validation_error", "message": "stage_id: Required", "param": "stage_id" } }

Reference

Every endpoint below is relative to the base URL https://api.kordic.io/api/v1 and requires Authorization: Bearer <key>. Each needs the matching scope (read for GET, write for POST/PATCH/DELETE).

Leads GET POST PATCH DELETE

# List leads — filters: stage_id, assigned_to, search, created_after, created_before
GET /leads?stage_id=STAGE_UUID&search=acme&page=1&per_page=20

# → 200
{
  "data": [
    {
      "id": "9c1f7e20-…", "workspace_id": "…", "company_name": "Acme Inc",
      "contact_name": "Jane Buyer", "email": "buyer@acme.com", "phone": "+14155551234",
      "stage_id": "…", "assigned_to": null, "deal_value": 5000, "currency": "USD",
      "tax_rate": 5, "lead_source": "website", "expected_close_date": null,
      "follow_up_date": null, "created_at": "2026-06-23T10:00:00.000Z", "updated_at": "2026-06-23T10:00:00.000Z"
    }
  ],
  "meta": { "page": 1, "per_page": 20, "total": 1, "total_pages": 1 }
}

# Create a lead — company_name + stage_id required
POST /leads
{ "company_name": "Acme Inc", "stage_id": "STAGE_UUID", "email": "buyer@acme.com", "deal_value": 5000, "currency": "USD", "lead_source": "website" }

# → 201
{ "data": { "id": "9c1f7e20-…", "company_name": "Acme Inc", "stage_id": "…", "deal_value": 5000, "currency": "USD", "created_at": "…", "updated_at": "…" } }

# Get / update / delete a single lead
GET    /leads/9c1f7e20-…        # → 200 { "data": { …lead… } }
PATCH  /leads/9c1f7e20-…        # body: any subset of fields → 200 { "data": { …lead… } }
DELETE /leads/9c1f7e20-…        # → 200 { "data": { "id": "9c1f7e20-…", "deleted": true } }

Contacts GET POST PATCH DELETE

# List contacts — filters: search, account_id
GET /contacts?search=jane&page=1

# → 200
{ "data": [ { "id": "…", "account_id": "…", "full_name": "Jane Buyer", "email": "jane@acme.com",
              "phone": "+14155551234", "title": "Head of Procurement", "linkedin_url": null,
              "created_at": "…", "updated_at": "…" } ],
  "meta": { "page": 1, "per_page": 20, "total": 1, "total_pages": 1 } }

# Create a contact — full_name required
POST /contacts
{ "full_name": "Jane Buyer", "email": "jane@acme.com", "account_id": "ACCOUNT_UUID", "title": "Head of Procurement" }

# → 201 { "data": { …contact… } }
GET /contacts/:id      # → 200 { "data": { …contact… } }
PATCH /contacts/:id    # → 200 { "data": { …contact… } }
DELETE /contacts/:id   # → 200 { "data": { "id": "…", "deleted": true } }

Accounts (companies) GET POST PATCH DELETE

# List accounts — filter: search
GET /accounts?search=acme

# → 200
{ "data": [ { "id": "…", "company_name": "Acme Inc", "industry": "Manufacturing",
              "website": "https://acme.example.com", "address": null, "country": "United States",
              "city": "San Francisco", "notes": null, "created_by": "…", "created_at": "…", "updated_at": "…" } ],
  "meta": { "page": 1, "per_page": 20, "total": 1, "total_pages": 1 } }

# Create an account — company_name required
POST /accounts
{ "company_name": "Acme Inc", "industry": "Manufacturing", "website": "https://acme.example.com", "city": "San Francisco" }

# → 201 { "data": { …account… } }
GET /accounts/:id      # → 200 { "data": { …account… } }
PATCH /accounts/:id    # → 200 { "data": { …account… } }
DELETE /accounts/:id   # → 200 { "data": { "id": "…", "deleted": true } }

Pipeline stages GET POST PATCH DELETE

# List stages — not paginated (returns the full ordered set)
GET /stages

# → 200
{ "data": [ { "id": "…", "name": "New", "position": 0, "is_won": false, "is_lost": false,
              "color": "#3B82F6", "probability": 25, "created_at": "…", "updated_at": "…" } ] }

# Create a stage — name + position required
POST /stages
{ "name": "Proposal Sent", "position": 3, "color": "#F59E0B", "probability": 60 }

# → 201 { "data": { …stage… } }
GET /stages/:id      # → 200 { "data": { …stage… } }
PATCH /stages/:id    # → 200 { "data": { …stage… } }
DELETE /stages/:id   # → 200, or 409 if leads still use it

Payments GET POST PATCH DELETE

# List payments — filters: lead_id, status=pending|confirmed. Each row carries a derived status.
GET /payments?lead_id=LEAD_UUID&status=confirmed

# → 200
{ "data": [ { "id": "…", "lead_id": "…", "amount": 2500, "currency": "USD",
              "payment_method": "bank_transfer", "payment_date": "2026-06-23T10:00:00.000Z",
              "recorded_by": "MEMBER_UUID", "confirmed_by": "MEMBER_UUID",
              "confirmed_at": "2026-06-23T11:00:00.000Z", "notes": "Deposit", "status": "confirmed" } ],
  "meta": { "page": 1, "per_page": 20, "total": 1, "total_pages": 1 } }

# Record a payment — lead_id, amount, payment_method, payment_date required
POST /payments
{ "lead_id": "LEAD_UUID", "amount": 2500, "currency": "USD", "payment_method": "bank_transfer", "payment_date": "2026-06-23T10:00:00Z", "notes": "Deposit" }

# → 201 — recorded_by is set to the member who created the API key
{ "data": { "id": "…", "lead_id": "…", "amount": 2500, "recorded_by": "MEMBER_UUID", "confirmed_at": null } }

GET /payments/:id            # → 200 { "data": { …payment incl. "status"… } }
PATCH /payments/:id/confirm  # → 200, sets confirmed_at + confirmed_by
DELETE /payments/:id         # → 200 { "data": { "id": "…", "deleted": true } }

Notes — log activities POST PATCH DELETE

# Write-only: create/update/delete notes on a lead. Read them via the activity timeline.
POST /leads/LEAD_UUID/notes
{ "content": "Customer requested a callback next week." }

# → 201
{ "data": { "id": "…", "lead_id": "…", "author_id": null, "content": "Customer requested a callback next week.",
            "created_at": "…", "updated_at": "…" } }

PATCH  /leads/LEAD_UUID/notes/:id   # body: { "content": "…" } → 200
DELETE /leads/LEAD_UUID/notes/:id   # → 200 { "data": { "id": "…", "deleted": true } }

Documents GET POST DELETE

# List a lead's documents (metadata) — not paginated
GET /leads/LEAD_UUID/documents

# → 200
{ "data": [ { "id": "…", "lead_id": "…", "document_type": "quotation", "name": "Quote Q-1001",
              "drive_url": "https://drive.example.com/q-1001", "storage_path": null,
              "file_size": null, "created_at": "…" } ] }

# Attach a link document — document_type, name, drive_url required
POST /leads/LEAD_UUID/documents
{ "document_type": "quotation", "name": "Quote Q-1001", "drive_url": "https://drive.example.com/q-1001" }

# → 201 { "data": { …document… } }

# Resolve a download target
GET /leads/LEAD_UUID/documents/:id/download
# → 200 { "data": { "type": "link", "url": "https://drive.example.com/q-1001", "name": "Quote Q-1001" } }

DELETE /leads/LEAD_UUID/documents/:id   # → 200 { "data": { "id": "…", "deleted": true } }

Activity timeline GET

# Unified, time-sorted feed for one lead (paginated)
GET /leads/LEAD_UUID/activity?page=1&per_page=50

# → 200 — type is one of: note · email · call · payment · document · whatsapp_message
{
  "data": [
    { "type": "call", "id": "…", "occurred_at": "2026-06-22T14:30:00.000Z",
      "actor": { "name": "Jane Agent" },
      "data": { "direction": "outbound", "status": "completed", "duration_seconds": 142 } },
    { "type": "payment", "id": "…", "occurred_at": "2026-06-22T11:00:00.000Z",
      "actor": { "name": "Sam Owner" },
      "data": { "amount": 2500, "currency": "USD", "payment_method": "bank_transfer" } },
    { "type": "note", "id": "…", "occurred_at": "2026-06-21T09:00:00.000Z",
      "actor": { "name": "Jane Agent" }, "data": { "content": "Left a voicemail." } }
  ],
  "meta": { "page": 1, "per_page": 50, "total": 3, "total_pages": 1 }
}

What's in the timeline

Notes, emails sent from the CRM, calls, payments, documents and WhatsApp messages — merged newest-first.
Inbound emails / full email threads and field-change history aren't included (planned for a later release).

Rate limits

Each key is limited to 1,000 requests per 15 minutes.
Every response includes RateLimit-* headers showing your remaining budget; exceeding it returns 429.

Revoking a key

Open Developer in the sidebar → click Revoke next to the key (Owner/Manager only).

On revoke

The key stops working within about a minute and cannot be reactivated.
Your CRM data is untouched — only that credential is disabled.

Still need help?

Our team responds within one business day — critical issues within four business hours.

Contact support →