Signalsby PressOne
Book technical discovery

Signals Omni · Developer Overview

Turn a completed call into data your systems can use.

Receive a call_completed webhook, retrieve the call through the Call Data API, and access the authorised recording from the systems that need it.

Call events · Call Data API · Recording access

Book an enterprise integration reviewExplore Signals OmniWebhooks documentation →

Signals Omni — voice integration

Diagram

Sources

PBXSoftphoneContact-centre platform

Signals Omni

Voice integration layer

Exposed primitives

call_completedCall Data APIRecording access

Destinations

CRMOmnichannelBIQAComplianceInternal systems

Signals supplies the event, record and recording · your systems supply the analysis

call_completed webhookCall Data APIAuthorised recording accessEnterprise integration review

Technical sequence

From a completed call to an updated system.

Integration sequence

  1. A connected call completes in your voice environment.

  2. Signals sends the call_completed webhook to your authorised endpoint.

  3. Your system uses the call identifier to retrieve the call information through the Call Data API.

  4. Your system requests authorised access to the recording where your workflow requires it.

  5. Your CRM, BI or internal workflow is updated by your own application logic.

Conceptual sequence

# Conceptual sequence only — not a production payload or endpoint.

1. call completes
2. POST  -> your endpoint            (call_completed event, call identifier)
3. GET   -> Signals Call Data API    (call information for that identifier)
4. GET   -> authorised recording      (retrieve or download)
5. your system updates CRM / BI / internal workflow

Refer to the current public documentation for exact schemas,
field names, authentication and endpoints.

Conceptual sequence, not a production payload or endpoint. Use the current documentation for exact schemas.

Webhooks →Voice API reference →Call recordings →

Integration review

We confirm how your environment connects before anything is configured.

The enterprise integration review confirms how your current PBX, softphone or contact-centre environment and your phone numbers connect to the Signals layer, and how completed calls and recordings are made available.

Signals does not claim universal plug-and-play compatibility. The review establishes the call path, the destination systems and the authorised access model before configuration begins.

You bring

  • Your current voice environment and numbering.
  • The systems that need the call data.
  • Your authorisation and retention requirements.

Signals brings

  • The completed-call event.
  • The Call Data API.
  • Authorised recording access.
  • The integration mapping to your systems.

Data boundary

Signals exposes the call. Your systems interpret it.

Signals exposes

The completed-call event, the call record and authorised access to the recording.

Signals does not

Transcribe, score, summarise or analyse the conversation in any way.

Your systems decide

What the call data means and which workflow, dashboard or record it updates.

Authorisation

Recording access is provided to authorised systems and business workflows only.

Managed enterprise integration

Omni is scoped with the team, not switched on from a dashboard.

  1. 01Enterprise integration review of your PBX, softphone or contact-centre environment, phone numbers and destination systems.
  2. 02Confirm how the connected calls and recordings are available to the Signals layer.
  3. 03Map the completed-call event, call record and recording to your systems.
  4. 04Configure the call_completed webhook endpoint.
  5. 05Integrate the Call Data API and authorised recording access.
  6. 06Test with controlled calls.
  7. 07Activate the production integration.

Omni is not activated through the self-service Developer Mode workflow used by Programmable Voice and Automations.

Related

Where Omni sits in the Signals platform.

Signals Omni

The enterprise voice integration layer: completed-call events, call records and authorised recording access.

Explore →

SIP Access

Signals SIP Access, our managed SIP trunking service, connects existing voice systems to the telephone network.

Explore →

Programmable Voice

Create and control calls from software with a Twilio-compatible API, OneML and webhooks.

Explore →

Automations

Turn business events into calls and capture the customer response.

Explore →

Omnichannel and Data Teams

Connect completed calls and recordings to omnichannel, CRM, BI and internal systems.

Explore →

Next step

Map your completed calls to your systems.

Bring your current voice environment and the systems that need its data, and we will map the completed-call event, call record and authorised recording access across your stack.

Book an enterprise integration reviewExplore Signals Omni