How to connect Binotel to X10CRM: lines, calls and recordings

Connect the API, choose a calling mode, map extensions and test calls and recordings.

Binotel setup covers API access, call routing, extension mapping and event delivery. Follow these steps in order. If you are choosing a calling setup, start with the Binotel integration overview.

#Before you start

  • Prepare your company’s Binotel Company ID, API Key and API Secret.
  • List customer-facing numbers and rep extensions. For calls through CRM telephony, obtain the SIP connection details.
  • Choose the X10CRM projects and users that will use the connection.
  • You need administrator access or permission to manage integrations. Agree on routing and event delivery with the implementation team.

Open Integrations → Binotel. The settings page on your CRM is /integrations/binotel/. If it is missing, ask the administrator to check your version and permissions.

#Step 1. Save the API connection

  1. Enter Company ID, API Key and API Secret in the API connection section.
  2. Select the relevant CRM projects. Start with an agreed test project.
  3. Enable the connection for testing and save the settings.
  4. Run the connection check. A successful check updates the extension directory and the last API verification time.

#Step 2. Choose the outgoing call mode

ModeWhat to configure
Configured CRM telephonyKeep X10CRM’s configured calling method. For Binotel browser calls, the implementation team registers its SIP line and assigns the number and routes.
Binotel callback to a SIP lineMap an extension to the user, check the lead’s project and grant the required permission to view customer phone numbers.

Saving Binotel credentials does not change your outbound number automatically. Make a test call and check the number shown to the recipient. For browser calling, see telephony setup.

#Step 3. Map extensions to reps

  1. After the API check succeeds, choose the option to add a line mapping.
  2. Select the X10CRM user and their Binotel internal number.
  3. Save and check the linked-lines table.
  4. Repeat for the relevant teammates. If extensions change, refresh the directory with the connection check and edit the mappings.

#Step 4. Check incoming routes

A number already handled by CRM telephony should route to the intended operator or group. Leave the separate external Binotel incoming-number field empty for that number.

If reps answer in Binotel softphones outside CRM telephony, enter the company numbers in the incoming-numbers field, separated by spaces in international format. Select one of the connection’s projects as the destination for those incoming calls.

#Step 5. Configure Binotel event delivery

  1. After saving the connection, find the Binotel webhooks section.
  2. If no address exists, use the action to create a webhook address.
  3. Copy the single address labelled API CALL SETTINGS / COMPLETED. Give it to the person configuring Binotel for both event types.
  4. Make a test call and check the last webhook time and the call log entry.

Copy the complete address from your CRM: it contains a connection secret. Do not publish it in documents or screenshots. If an administrator rotates that secret, update the address in Binotel too.

#Step 6. Test with a rep’s account

  1. Call from a test lead. Check the selected line, outbound number and audio in both directions.
  2. Test an incoming call from a known customer and another from a new number. Check routing and the linked lead.
  3. Make a missed call and check the log.
  4. After a completed call, check its history entry and ensure the log has no duplicate.
  5. When audio is available, test playback with an authorised role. Test transcription separately if required.
  6. If phone numbers must be hidden, test the entire route and workstation. Direct callback is unavailable without permission to view phone numbers.

#Where to find recordings

Calls appear in the shared log and lead history. Binotel audio downloads in the background and may arrive later. Calls through CRM telephony use its recording mechanism. Access depends on user permissions.

A logged call does not mean its transcript is ready. Transcription requires available audio, a configured provider and completed processing. See recordings and transcription.

#Common problems

ProblemWhat to check
Connection check failsCompany ID, API Key, API Secret and API access for the Binotel account.
Extension missingRefresh the directory and confirm the extension exists in Binotel.
Callback unavailableCallback mode, user-to-line mapping, lead project and permission to view phone numbers.
Wrong outbound numberThe CRM telephony route and outbound number. API credentials do not configure these.
Call in Binotel but not X10CRMWebhook address, last event, projects and logging numbers. Ask the implementation team to check background reconciliation.
Call entry but no audioRecording availability in Binotel, background download and user permissions.
Duplicate or incorrectly linked callNumber routing, destination project and transfers. Give support the time and identifier of the test call.

When contacting support, provide the call time, mode, CRM user and observed result. Do not include API credentials, SIP passwords or the secret webhook address in ordinary messages.