Skip to main content
Larynth’s checks help you follow calling rules. They do not make a call lawful on their own, and Larynth does not promise compliance. You are the caller. Your legal responsibility stays with you. Ask your own lawyer about your situation.

​
Checks before an outbound call

Every outbound call, from a campaign or from POST /v1/calls, goes through these gates before it dials: Outbound calls to emergency numbers (911) are blocked.

​
When a call is refused

A refused call returns an error with a stable code that names the rule, for example dial.window.closed. When the refusal is about calling hours, the error includes retry_at, the next moment the call may be allowed. GET /v1/compliance/decisions lists every pre-dial decision, with the rule, the result and the time. Use it to see why a contact was not dialed. Record consent with POST /v1/compliance/consents. A record needs:
  • the number (e164) and the kind: express or express_written
  • when it was granted (granted_at) and how it was captured (source)
  • evidence: an evidence_ref or evidence_text
  • a scope: the whole account, or one campaign
Consent records are kept and cannot be deleted by you.

​
Opt-outs and Do-Not-Call

  • POST /v1/compliance/revocations records that someone withdrew consent. The number is added to your internal Do-Not-Call list.
  • POST /v1/compliance/dnc adds a number to your internal list directly.
  • Larynth keeps its own opt-out list, fed by opt-outs on calls, and applies it to every account.
  • The agent can end a call and record an opt-out with the opt_out tool.

​
What stays with you

  • You follow the laws that apply to your calls.
  • You bring your own Do-Not-Call registrations for outbound campaigns.
  • You only call people who gave the consent your calls need.
  • You tell your own staff that calls are recorded.
  • You review the terms and the acceptable use policy for your situation.
See Outbound with consent for the working steps.