Integrations

Results land where you work.

An approved outcome is an event you can send to a calendar, a mailbox, a CRM or your own system. During onboarding we decide together what to connect first.

Google Calendar and Microsoft 365

A meeting from the call lands in the employee's calendar after approval, with a description and a quote from the call.

E‑mail

A draft message to the customer with the outcomes. Open, edit, send. It never goes out on its own.

CRM via API and webhooks

Every approved outcome as a JSON event to your endpoint. Signed, retried on failure, idempotent.

Export and reports

CSV with calls, outcomes and metrics. For spreadsheets, BI, billing.

Notifications

SMS, e‑mail or a text‑to‑speech call to the team when an incident needs a response.

Monitoring stations

A Contact ID / SIA bridge to station software, so a phone report looks like a panel signal. In preparation.

A webhook in practice

This is what an approved outcome looks like when sent to your system.

POST https://twoj-system.example/tidyvoice
X-TidyVox-Signature: sha256=…

{
  "zdarzenie": "ustalenie.zaakceptowane",
  "rozmowa_id": 4821,
  "linia": "+48220000000",
  "pracownik": "anna.k@firma.pl",
  "typ": "spotkanie",
  "kiedy": "2026-09-29T15:00:00+02:00",
  "klient": { "telefon": "+48601…", "email": "kowalski@firma.pl" },
  "cytat": "We wtorek po piętnastej będzie dobrze.",
  "zaakceptowal": "anna.k@firma.pl",
  "zaakceptowano_o": "2026-09-23T11:34:02+02:00"
}

Nothing leaves without approval. The webhook receives only outcomes confirmed by a human. Proposals stay in the panel.

Retries and idempotency. No 2xx response means a retry. Every event has a stable identifier, so two deliveries never create two meetings.

A signature. Every request is signed with a shared secret. You reject anything that fails verification.

Have a CRM that isn't on the list?

If it accepts webhooks or has an API, we connect it during onboarding.

Write to us