Zoho CRM
Zoho runs a very large number of small and mid-sized businesses in the region, frequently alongside the rest of the Zoho suite, and frequently with one person who understands the configuration.
Zoho runs a very large number of small and mid-sized businesses in the region, frequently alongside the rest of the Zoho suite, and frequently with one person who understands the configuration.
What Zoho CRM holds, and why that matters here
Zoho CRM is inexpensive, highly configurable and widely adopted across the Gulf SME market. Deployments tend to be customised heavily and documented lightly, which concentrates knowledge in very few people.
That concentration is the argument for an assistant. The questions are ordinary — deal status, contact history, what was quoted — and the cost of each interruption is high because the person being interrupted usually has another full-time job.
- Leads and contacts — the record and its source.
- Deals — stage, value and expected close.
- Quotes and invoices — what was offered, where the finance module is used.
- Activities — calls, tasks and follow-ups.
- Custom modules — usually substantial in a Zoho deployment.
Questions Elbi can answer from Zoho CRM
What is happening with this deal?
Stage and next step, answered directly.
Who is this contact?
Record and history for someone about to make a call.
What did we quote?
The quote on record, which settles disputes.
What follow-ups are due?
Task and activity status for the person who owns them.
Capture this lead
Writing an enquiry onto the record with its context.
What is our pipeline?
Summary by stage without building a report.
How Elbi connects to Zoho CRM
- An OAuth client in Zoho's API ConsoleThe connection is registered as a client in the Zoho API Console, where your administrator generates the grant that yields a refresh token. Nothing is installed inside the CRM; the client and its secret stay in your Zoho account.
- Scopes by module and operationZoho scopes are granular: read access to Deals, Contacts and Quotes can be granted on its own, and write access to Leads only if capture is enabled. The scope list becomes the first written answer to "what can it reach?"
- The authorising user's profile still appliesA Zoho token acts with the permissions of the user who authorised it. That user's profile and role, and your data sharing rules, set the outer limit; the asking person's own access narrows answers further inside it.
- Your data centre, your endpointsZoho hosts accounts in regional data centres, each with its own sign-in and API addresses. The connection is configured for the data centre your account lives in.
- API names become your labelsCustom modules and renamed fields come back from the API under their API names, not the labels your team knows. The reply uses your labels and picklist values, in Arabic or English to match the question.
- Capture creates a Lead, not a ContactWhere capture is enabled, an enquiry becomes a Lead with the conversation in a note, so your assignment rules and Blueprint can take it from there. Converting it into a Contact, Account and Deal stays with the salesperson.
Zoho CRM profiles, roles and control
| Direction of access | Read by default. Creating Leads, logging a call or adding a note needs the matching write scope and is enabled per action, with optional human confirmation. Converting leads and editing deals stay with your team. |
|---|---|
| Modules and fields | Limited twice: by the OAuth scopes on the client, and by the profile of the authorising user, including field-level permissions that keep fields such as margins or ID numbers out of reach. |
| Roles and sharing rules | Zoho's role hierarchy, data sharing settings and sharing rules decide which records each user sees, and answers stay inside the asking person's access. |
| Credentials | The client ID, secret and refresh token belong to your Zoho account. Your administrator can revoke the token or delete the client in the API Console without involving us. |
| Where data goes | Records fetched for a question serve that answer and are not duplicated into another store. Anything said in the conversation is destroyed within 24 hours, most often when it closes, and is never passed to an external AI service. |
| Audit | Each lookup can be recorded with the question behind it. For anything that writes, Zoho CRM's own audit log shows the change on your side. |
| If it is unavailable | If Zoho cannot be reached, or the day's API credits for your edition are used up, the assistant says it could not check and offers a person. |
What this replaces
The pattern in Zoho shops mirrors other SME systems: high-value data, narrow access, and one or two people who become the bottleneck for every routine question. The assistant removes the routine layer without touching the judgement.
Because Zoho is usually customised extensively, mapping matters more here than in a standardised product. Custom modules and renamed fields are the norm rather than the exception, and deciding which of them the assistant should read is a business conversation.
Lead capture is the second case. SMEs lose enquiries out of hours more than larger organisations do, because there is no overnight team to catch them.
Which Zoho businesses use it, and for what
Professional services
Client and deal history for small teams.
Trading and distribution
Quote and pipeline questions.
Agencies
Contact history before a call.
Any Zoho SME
Lead capture outside working hours.
Where to begin with Zoho CRM
Zoho accounts tend to have one person who knows the configuration and ends up answering for it. The first questions to connect are the ones that land on that person most: what stage a deal is at, what was quoted, and which follow-ups are overdue. Each is a single-module read, and each currently costs that person's attention.
Lead capture outside working hours is the second opening, and for many SMEs the more valuable one. An enquiry that arrives at night becomes a Lead with the conversation attached, ready for whoever opens Zoho in the morning, instead of an unanswered chat.
Pipeline summaries by stage are fine for a quick check. Anything that needs targets, formulas or comparisons between periods belongs in CRM reports or Zoho Analytics, not in a chat reply.
What connecting Zoho CRM involves
- Start with the person who knows the setupIn most Zoho accounts one person understands the custom modules, renamed fields and Blueprints. An hour with them early is worth more than any mapping done without them; the question list is agreed with them and with whoever owns the customer data.
- Register the client and choose scopesYour administrator registers the client in the API Console, selects module-level scopes for the agreed questions and generates the grant. The secret and tokens remain yours to rotate or revoke.
- Check the authorising user's profileBecause the token carries that user's permissions, confirm the profile does not reach modules or fields outside the list. If it does, narrow the scopes rather than relying on the assistant to ignore what it can see.
- Map modules, layouts and picklistsCustom modules, multiple layouts, picklist values and fields renamed over the years are mapped to the questions they answer, with Arabic wording agreed for anything a customer will hear.
- Rehearse before it goes liveZoho CRM offers a sandbox on some editions; where you have one, rehearse there. Try a deal owned by someone else, a lead that already exists as a contact, a quote in a custom stage, and Zoho unreachable.
- Launch on one module, then add scopesStart with Deals or Leads, watch a month of real questions, then add modules by extending the scopes. Each extension is a change your administrator makes, and can undo.
Personal data in Zoho CRM and the PDPL
SME CRMs gather personal data without anyone deciding they should: mobile numbers on Leads, an ID number in a custom field someone added for a quotation, notes about a customer's circumstances. Under the Saudi Personal Data Protection Law, reading those through an assistant needs a purpose and a basis like any other processing.
Zoho gives you two precise controls: module-level scopes on the client, and field-level permissions on the authorising user's profile. Between them, fields no question needs never reach the assistant. On Elbi's side, what is said in the chat is destroyed within 24 hours, typically as the conversation closes, and Zoho remains the system where records are kept, corrected and deleted.
Zoho CRM's data privacy settings can record a data processing basis on each record where you enable them. If you use them, capture from chat should fill them in rather than leave them blank, and the chat should tell people, in their own language, that their details may be saved.
What organisations typically see
Zia, SalesIQ and where Elbi fits
Zoho has its own AI and chat tools. Zia, the assistant built into Zoho CRM, offers predictions, suggestions and conversational queries for people working inside the CRM, and Zoho SalesIQ provides website chat with a bot builder that integrates with Zoho CRM. For an organisation that has standardised on Zoho, keeping everything with one vendor is a genuine simplicity.
For Saudi SMEs the practical checks are the same as for any option: how well the Arabic holds up on real customer messages, dialect included; where language processing happens, and whether that sits well with your PDPL position; and whether the assistant needs sources outside Zoho, such as a policy document or an accounting system, in the same conversation.
Elbi answers those the same way for every system it connects to: Arabic and English as first languages, conversation processing inside the Kingdom on infrastructure you control, no external AI service. Zoho stays the record; Elbi answers from it and captures into it. If SalesIQ already runs your website chat, decide which channel each tool owns before adding the other.
The mistake that costs Zoho SMEs most is authorising the connection with the administrator account because it is the one that works. It works because it can see everything, which is exactly what the security review will ask about.
Common questions
Expected. Custom modules and fields are mapped during deployment.
No. The assistant uses a scoped integration rather than a user seat.
Where you scope it to. Most deployments start with CRM.
The one your account is in. Zoho runs regional data centres with separate sign-in and API addresses, and the connection is configured for yours during deployment.
Those of the user who authorised it. That is why the authorising user's profile is checked during deployment, and why the scopes are narrowed to the modules the questions need.
It can. A Lead created through the API can be set to trigger your workflow rules and Blueprint as a web form entry would, which is usually what you want. That choice is made per action during deployment.
Connect Elbi to your Zoho CRM
A working assistant on your own deals, leads and quotes, in Arabic and English.