Integrations
Creatio contact center integration
Your sales and service teams get Creatio and telephony working as one system. The account manager who owns the customer gets the call first, the agent sees the contact and open cases before answering, and the call outcome and audio land in the CRM right away. A call from an unknown number becomes a lead, and a call about an open issue is added to the existing case. We connect telephony and messaging apps through Creatio's APIs without touching its base configuration.
ContactPaul Morganfound in CreatioAccountVector LLCcustomerCaseSR-2207openOwnerEmilyavailableCapabilities
What you get with Creatio
Examples
How teams use it
Three everyday situations in sales and service.
A lead from a call
Someone who isn't in Creatio calls. The agent answers and fills out a short call form, and a lead appears in Creatio with the source set to Call and the ad campaign filled in. Creatio's rules assign a manager, and the call audio is available right in the lead.
- Lead from the agent's call form
- Source and campaign filled in
- Recording in the lead record
Roomnot foundnewLeadin CreatiocreatedSourcecall, adfilled inRepper rulesscheduledA call adds to an open case
A customer calls about a case that's already open. The call goes to the case owner and, if they're busy, to the tier 2 group. The conversation and its recording are added to the case history, so the next person sees everything that's been discussed.
- Case owner first
- Then the tier 2 group
- Call in the case history
CaseSR-2207openAssigneeMikebusyGrouptier 2 serviceacceptedCasecall addedin CreatioLine workload in reports
The service manager checks how many calls were answered today, how long customers waited, and how many cases came from calls. Missed calls go to the callback list, and each one leaves an activity in Creatio.
- Answered and missed calls
- Hold time on the line
- Cases created from calls
Calls412acceptedWait18 s avgnormalInquiries96 from callsin CreatioMissed7callbackManager assignment rules are set up in Creatio and aren't duplicated in the platform.
How it works
Setups, routing, and data sync
Setups
Where your team works
Sales can work right in Creatio: an incoming call opens the contact record. The contact center line answers from the CONTACT.WORK interface, with the Creatio fields you need pulled into the call form. Both setups can run at the same time for different departments.
- Creatio record opens on the call
- Creatio data in the call form
- Different setups per department
In Creatioscreen popsalesIn CONTACT.WORKCreatio data in call formlineMixedby departmentside by sideCreatio cloudvia APIcheck accessRouting
Who gets the call
The call goes first to the account owner listed on the account record or to the owner of the open case. If they don't answer, the call moves to the department group. Calls from unknown numbers are distributed among all agents.
- Account owner first
- Case owner
- Then the department group
Ownerfrom recordfirstOpen caseassigneefirstNo answerdepartment groupnextNew numbershared queuedefaultSync
Through Creatio's APIs
The platform syncs with Creatio through its OData and web services, using a single integration user. A separate package adds call buttons and the line panel inside Creatio; the base configuration doesn't change.
- OData and web services
- One integration user
- UI package on request
ProtocolOData and web servicesCreatioUserfor synconeEventscalls and summariesin CreatioPackageinto configurationon requestSetup
How we connect Creatio
- 01AssessmentWe look at which Creatio sections you use and which processes depend on calls.
- 02DesignWe decide who works directly in Creatio and who works in the platform interface.
- 03AccessThe sync needs one service account – your agents don't need Creatio licenses.
- 04FieldsWe map the agent's call form to contact, lead, and case fields so data is never entered twice.
- 05RoutingWe set up calls to go to the account manager or case owner and, if they're busy, to the department group.
- 06TestingWe check how activities, leads, and cases appear in a test environment, and only then move the settings to production.
Requirements
What you'll need on the Creatio side
- Creatio
- Any deployment with API access
- Access
- A Creatio user for the sync
- Environments
- Test and production – we verify settings before moving them
- Telephony
- Your current telephony stays in place
- Platform
- Our cloud or your own server – your choice
- Billing
- Setup hours under your support plan
Preparation
What to have ready
Q&A
Frequently asked questions
What will the agent see when a call comes in?
The contact, the account, open cases, and the account manager – all before picking up.
Will calls be saved in Creatio?
They will. After each call, Creatio logs an activity with the audio, duration, and outcome.
Can calls generate leads?
A call from a new number immediately becomes a lead with its source and campaign, and Creatio's rules take it from there.
How is a call linked to an open case?
If the caller has an open case, the case owner takes the call, and the conversation and audio are attached to the case.
Do we have to buy Creatio licenses for agents?
No. Agents on the line work in the platform interface, and the sync runs under one technical user.
Do you change the Creatio configuration?
Your Creatio configuration stays untouched. Call buttons inside Creatio come from a separate package that can be removed entirely.
Does it work with Creatio in the cloud?
It does, as long as the platform can reach Creatio's APIs over the network. We confirm this during the assessment.
Will messages from messaging apps reach Creatio?
They will. Everything the customer sent on WhatsApp, Facebook Messenger, Telegram, or web chat is stored with the contact next to calls.
How is connecting Creatio different from other CRMs?
The approach is similar; versions and APIs differ. For each system, we test the setup in its own test environment.
How is Creatio integration billed?
The platform has no license fees, and the work is billed under your support plan. The scope depends on your Creatio products and setup – we'll estimate it once we've seen your system.
Glossary
Terms on this page
- API (application programming interface)
- The way programs exchange data with each other without a person in the loop. Learn more →
- Cloud deployment (cloud)
- The platform runs on the vendor's servers, and agents connect over the internet. Learn more →
- CRM – customer relationship management
- Where a company keeps its customers, deals, and full communication history. Learn more →
- Customer record
- The screen of customer data an agent sees during a conversation. Learn more →
- Callback
- The customer doesn't wait on hold but asks for a callback – and gets one when an agent is free. Learn more →
- On-premises deployment
- The system runs on the company's own servers, not in the vendor's cloud. Learn more →
Updated: