Zoho Desk Consultant, Kenya

Calls, WhatsApp and SMS from customers on mobile

In Kenya the phone is the customer's main support tool. Customers call the number they have, message a technician they met once on WhatsApp, or reply to an SMS notification. A desk designed only around email misses most of this traffic.

How I bring mobile channels into Zoho Desk:

• Voice. A cloud phone system connected to Zoho Desk can open a ticket for each call and keep the recording with it. I verify whether the provider you use or plan to use offers that integration for Kenyan numbers, rather than assuming it.
• WhatsApp. WhatsApp reaches Zoho Desk through its instant messaging channel options, using business messaging from approved providers with rules on templates and response windows. Confirm availability, edition and costs with Zoho for your account, then test with a real business number.
• SMS. Outbound updates such as ticket received or technician on the way can go through an SMS gateway integration; inbound SMS needs a provider that can pass messages to the desk.
• A single public number and handle, so customers stop messaging individual staff.

Once channels converge, every contact becomes a ticket and personal phones stop being the system of record. The global Zoho Desk page explains the product in general; sales inquiries should route to Zoho CRM rather than sit in the support queue.

Swahili and English replies, checked by native speakers

Many Kenyan customers switch freely between English and Swahili, and many mix the two. Some prefer another local language. Replying in the language the customer used makes a support interaction feel human, especially for consumer businesses outside the capital.

How I design for it:

• Language as a ticket field, set from the channel or by the agent, so tickets can be routed and reported by language.
• Template pairs. Common replies such as acknowledgment, payment confirmation, technician scheduling and closure exist in both English and Swahili, with the same meaning and tone.
• Help center articles for the most frequent questions in both languages, starting with the few that generate the most tickets.
• Tone for each channel. A WhatsApp reply reads naturally; an email to a corporate client remains formal.

The engagement runs in English. Swahili and any other local-language wording comes from, or is reviewed by, native speakers in your company or at a local partner, and I build the structure so they can update wording without touching rules. Machine translation can help agents understand an incoming message, but customer-facing templates should always be reviewed by a person who speaks the language natively.

Agents' language skills become part of the assignment rules, so a Swahili ticket does not wait in a queue for someone who will reply in English.

Payment queries, M-Pesa references and the ledger

Many support requests in Kenyan businesses are about money: I paid but my account is not updated, I sent to the wrong paybill account number, I was charged twice, please confirm my balance. These tickets need finance, and they need the transaction reference.

A payment query flow in Zoho Desk:

• A dedicated ticket type requiring the M-Pesa transaction code or bank reference, amount, date and the account or invoice it was meant for.
• Ledger context. Through the integration with Zoho Books, the agent can see invoices and recorded payments for the customer. If the payment is not there, the ticket moves to finance.
• Finance queue with a deadline, so unallocated payments are investigated rather than left in a suspense account.
• Reversal and refund requests following a controlled approval, never handled informally in chat.
• Templates that confirm resolution with the reference, so the customer has a clear record.

Agents should never ask customers for PINs or full card details, and templates say so. Reports on payment tickets by cause, such as wrong account number or delayed posting, often show where the payment instructions on invoices or the matching rules in the ledger need fixing. The business automation page covers automated receipt matching.

Service hours upcountry, SLAs and field visits

A response promise that works in Nairobi may be impossible in Turkana or on the coast. When support involves sending a technician, installer or surveyor, SLAs have to reflect distance, road conditions and how many people you have in each region.

What I configure:

• Regions as a ticket field, set from the customer's location, driving both assignment and SLA.
• SLAs by region and service type: a remote fix, a scheduled visit and an emergency call-out carry different targets, based on what you can actually deliver.
• Business hours and a Kenyan public holiday calendar, so SLAs pause when the desk is closed and customers get an honest auto-reply.
• Field visit handoff. Tickets needing a visit become scheduled jobs with notes, parts and photos captured on closure, using Zoho Desk's own features or a field service tool linked to it.
• Escalation before breach, going to the regional supervisor in time to rearrange the schedule.

For field teams on the road, the Zoho Desk mobile app lets technicians update tickets and add photos. Connectivity varies, so I test what works on their phones along real routes. Where field service becomes the main business, with parts, routes and job costing, a dedicated field service app or ERP may be needed; see ERP for field service.

Ticket data under Kenya's data protection law, and when Desk is not enough

Tickets collect personal data: names, phone numbers, ID numbers for account checks, locations, payment references and photos of premises. Under the Data Protection Act, your organization must process that data lawfully and securely, and your data protection officer or advisor decides how. In Zoho Desk I then:

• Limit which agents see which departments, fields and attachments.
• Keep templates from asking for more than is needed.
• Set retention and deletion rules for old tickets and files.
• Restrict exports and integrations to named administrators.
• Ask Zoho where your Desk data is hosted, so your advisor can assess the cross-border transfer question.

Zoho Desk also has limits. Big call centers rely on scheduling, outbound dialing and call quality tools that come from specialist platforms. Telecom-scale operations may need carrier-grade systems. A subsidiary may be required to use its group's service platform.

Work happens remotely and in English, with workshops in overlapping working hours and recorded sessions for supervisors in the field. Visits are possible only by arrangement. If the wider question is how sales and service share data, see my CRM consultant Kenya page, or start with the Kenya overview and wider Zoho in Kenya notes.