Integrations
The call ends. The work lands in your systems
iCall alerts your team on Telegram about each new request, and every record also shows on the call page. Writing to Google Sheets and an SMS after the call are being prepared: they cannot be switched on yet.
Trial: 7 days and 60 minutes, with no card. It starts at your first test call from your phone
After the call, the manual work begins
Someone re-types the booking
A visit, an order or a phone number moves by hand into a sheet. One step is nothing when calls are few and a lot when calls are many.
Your team hears late
The request is in one place, the call in another. Whatever you are not told about in time is often handled late.
Your team has to hunt for the result
After a call someone has to open the record and find what the customer needed. An alert shows it right after the call.
How a connection comes to life
Step 1
Choose whom the assistant alerts
Which team member or group gets the alert about a new request.
Step 2
Connect your account
A team member links the Telegram bot with a one-time link. We never ask for a system password.
Step 3
Test it and switch it on
After a test call the alert should arrive in Telegram and the record should show on the call page.
What switches on and what is being prepared
Telegram switches on once a team member links the bot, so its status is in setup. Google Sheets and an SMS after the call are being prepared. We do not show connections to other systems on this page.
Google Sheets
A new row for each call and request in your spreadsheet. It cannot be switched on yet
Coming soonSMS after the call
A short text to the caller after the call. It cannot be switched on yet
Coming soonTelegram
Your team gets a Telegram message about a new request or call. A team member links the bot with a one-time link
In setup
Control rules
An integration does not mean the assistant may do anything.
Only the actions you allow
The assistant uses only the connections you switch on
No system passwords
You add a connection by connecting your own account
No personal data from a phone number alone
An order status or personal details are never given out just because the caller's number matches
Call → Action → Evidence
One call, from a visit request to the team alert. The example uses a fictional clinic.
- Call
A patient asks for a visit
I would like to see a doctor tomorrow evening
Inbound call, 19 Oct, 14:05
- Action
What the assistant does after the call
- Recorded the visit request as a separate entry
- Alerted the team on Telegram
- Saved the request on the call page too
- Evidence
What the workspace shows
- Request
- Visit, tomorrow evening
- Team alert
- Telegram, sent
- Call page
- Transcript and summary
ExampleDemo data: a fictional clinic and record. This is an illustration, not a real call
Questions about integrations
Let's connect your systems
Tell us which system you work with and we will work out what can be switched on.
Trial: 7 days and 60 minutes, with no card. It starts at your first test call from your phone
More modules
iCall is one platform: phone lines, knowledge, actions and evidence work together
- Phone lines and SIPYour number or any carrier's SIP trunk
- Knowledge baseFrom your website, your documents and your calls
- Call evidence and qualityTranscripts, action receipts and review
- Campaigns and remindersOutbound calls with consent; not switched on yet
- SurveysCSAT after a visit; NPS planned, not switched on yet
- When a person is neededA message to your team; direct transfer is planned
- Security and trustData location, access and AI disclosure
- Why iCallMarket, product, moat, business model and roadmap