Zoho CRM setup does not end with opening an account: opening Zoho takes minutes, but a setup that fits your business depends on getting a series of decisions right. From license architecture to the role scheme, every decision either speeds your work up six months later or blocks your way. On this page we have written out those decisions, the mistake we see most often in the field, and where we stand.
20business days
Starts after scope approval; the date is written into the scope document.
3channels
Base support after go-live, not priced separately.
48hours
A written proposal after the discovery call.
We listed the twelve decisions that decide the fate of a Zoho setup. Every row has the same three things: the decision itself, the mistake we see most often in the field, and our choice, with the reasoning. You may disagree; then we talk it through at discovery and weigh the reasoning on both sides.
Setup plan01 · License architecture
01 12
Zoho One, CRM Plus, or a single product?
Common mistakeSaying “let's get the most comprehensive one” and moving to Zoho One. Most of the 50+ applications paid for per user are never opened; the invoice arrives every month, the usage never does.
Our choiceWe do a role-based count: who actually touches how many applications, laid out in a table. The breaking point is usually five applications per user; below that, single licenses are cheaper.
02 12
Standard module or custom module?
Common mistakeSqueezing appointments into Events and procedures into Deals. It works for the first three months, then the report you want never comes out; the fields were created for another purpose.
Our choiceIf a record has its own lifecycle, its own date, and its own status, we open a custom module. In a health tourism agency, appointments and procedures live separately; they become separate modules.
03 12
Who is a lead, and when does it become a contact?
Common mistakeOpening every form submission directly as a Contact. There is no funnel, so there is no conversion rate either; which channel brings real customers stays invisible.
Our choiceLead = a request not yet qualified. We tie the moment of conversion to a single event, not to a person's discretion: for example, automatic conversion when the first call is completed. That way every record passes through the same door.
04 12
Who changes the stage?
Common mistakeMaking the stage a picklist the user selects by hand. Everyone advances it at a different time, the funnel lies; management cannot trust the number it sees in the report.
Our choiceA stage is an output, not an input. Real events advance the stage automatically (quote sent, payment received, appointment created). The user does the work, the system writes the stage.
05 12
Where should the process be enforced, and where should it flow automatically?
Common mistakeBuilding everything with workflows. Once the rule count passes forty, no one knows what triggered what or why; turning off one rule breaks something elsewhere.
Our choiceIf a behavior is expected from the user, Blueprint; if a reaction is expected from the system, workflow. If both touch the same field, Blueprint wins; we map the conflict out from the start.
06 12
Who will see whose records?
Common mistakeGiving everyone the Administrator profile for the sake of speed. “Let's leave it like this for now” becomes permanent: everyone sees every record and can delete any field.
Our choiceWe map data visibility first and write the roles after: who should see which record, who should edit which field. Where there is a branch or region split, the role hierarchy alone is not enough; Territory comes into play.
07 12
What do we migrate, what do we leave behind?
Common mistakeImporting the old system as is. Duplicate records and empty fields move into the new system on day one; the team sees the same person in two records.
Our choiceDeduplication and normalization before the migration, a count reconciliation after it. Which record was left out and why is reported too; there is no argument about lost records.
08 12
Separate organizations, or a single org?
Common mistakeOpening a separate organization for every branch. Consolidated reporting becomes impossible, license costs double; the same person becomes two records in two branches.
Our choiceSingle org + Territory + branch-based layouts. Management follows the whole from a single screen. A separate organization only makes sense when there is a separate legal entity, separate accounting, and a separate data controller.
09 12
Whose name does the correspondence sit under?
Common mistakeConnecting personal Gmail accounts over IMAP and leaving it there. When the person leaves the company, the correspondence history leaves with them; email sent from an unverified domain may never arrive.
Our choiceOrganization email, SPF/DKIM verification, and record-based association. Correspondence sits under the record, not the person; when the person leaves, the account closes and the history stays in place.
10 12
How do conversations enter the system?
Common mistakeTyping calls and WhatsApp messages into notes by hand. If there is no record, there is no channel performance either: how many calls were made, which message turned into an appointment, none of it can be measured.
Our choiceZoho Voice or integration with your existing phone system, and WhatsApp flowing into the CRM automatically. A record opens the moment the conversation starts; when it ends, duration and outcome are written; the channel report fills without manual data entry.
11 12
Where does consent live, and who accesses the data?
Common mistakePutting the explicit consent text on the form and storing the consent nowhere. There is no record to show in an audit: who consented, when, and to which text has no answer.
Our choiceConsent date, channel, and text version are kept as fields on the record. Health data is a special category of personal data under KVKK (Turkish data protection law); we restrict access at the role level and define the retention period during the setup.
12 12
Which questions will you ask?
Common mistakeLeaving reports for last. After the fields are built, “we can't measure this” comes up, and going back is expensive: filling past records with a new field is hard.
Our choiceIn the first week we write down the eight questions you want answered: which channel brings customers, where the losses happen, and so on. The field schema is built backwards from those questions; the report is the input of the setup, not its result.
The user does the work, the system writes the stage. All twelve decisions are this clear: said in one sentence, applied in the setup.
Discovery and the proposal are not counted: in a free 30 minute discovery call we clarify your current processes and what the system needs to include, and within 48 hours you have a written proposal with the scope and the fee. Once you approve the scope, the clock starts; Day 1 is the first business day after scope approval, the Zoho setup goes live in 20 business days and the date is written into the scope document. Below you see which day each step starts and which day it ends. If we build the brief together, this work happens before scope approval and is not counted in the 20 business days; we tell you clearly at the end of discovery how long it will take.
- Day 1
Kickoff
The first business day after scope approval. We go through the approved scope with your team and list the prerequisites on your side (access, data, a decision maker); the go-live date is already written in the scope document.
- Days 2-4
Design
We document which Zoho products will be used, the module structure, custom fields, role scheme, and data flow. Each of the twelve decisions is written out one by one in this document; we do not move to setup until you approve it. The Zoho One, CRM Plus, or single-license decision is also settled at this step; unnecessary license costs are eliminated from the start.
- Days 5-12
Setup
Zoho environment fully activated, users defined, modules configured; email, calendar, and telephony connections in place. Every item in the design document is worked through in order; workflows and Blueprints are written at this step, and the first reports are built here too.
- Days 13-17
Data and UAT
Data from your old system is cleaned, imported into Zoho, and tested together with your team. Tests run on demo records and follow your team's real business scenarios; your live data is never at risk, and every fix that comes up is closed before anything goes live.
- Days 18-20
Go-Live
Delivered with department-based live training sessions, video recordings, and a Turkish user guide. Each team learns only its own screens; the training recording and the guide stay with you for employees who join later.
- From day 21
Base support after your Zoho setup is not priced separately.
Feature and customization requests you send by email in the first 6 months are part of the setup, with no limit on their number; new modules and new integrations are quoted in writing at a fixed fee before work starts. The team that did the setup is the team that gives support; your question is answered by someone who knows the system.
Six items, one proposal. Every item is finalized in a written proposal after discovery; no surprise line items. The list below says what you will have in hand at the end of the Zoho setup.
- 01
Zoho Environment
Account setup and product activation; domain verification, organization settings. Currency, time zone, business days, and company details are entered correctly from day one; these are the settings that are tedious to fix later.
- 02
Users and Roles
Department-based user provisioning, role and profile definitions, hierarchy and data visibility rules. Who sees what, who edits what, who exports what: all of it is documented in a table and is in your hands at handover.
- 03
Module Configuration
Custom fields, layouts, and workflows built around your business processes; initial dashboards and reports delivered ready to use. Field names in your own language, mandatory fields according to your own process; the team recognizes its own work the first time it opens the system.
- 04
Data Import
Data export from Excel, legacy CRM, or accounting software, deduplication, normalization. Then a count reconciliation: how many records were in the source, how many entered Zoho, how many were left out and why, all in a single report.
- 05
Integrations
Gmail / Outlook / IMAP integration, calendar sync, telephony connection. WhatsApp is connected as well. Correspondence, appointments, and calls gather under the record; the team does not switch to another screen to find information.
- 06
Training and Handover
Department-based live training, video recordings, Turkish user guide. Plus an adoption report: we measure whether the team is actually using the system; if a screen goes unused, we find out why and fix it.
Open your Zoho account through Eksenium
The license fee does not change; your account is opened under an authorized partner registration. We are your point of contact throughout setup and support; you bring your license questions to us as well.
You start with the trial; if you decide to go ahead, you continue on the same account, and nothing that was built is redone.
Nothing describes what a setup is worth better than the customer's own words. Each row is a single customer's words: on the left how they describe the way they worked before the setup, on the right how they describe today. The quotes are taken as is from published case studies and reviews.
All On Dental
Before the setup: “Everything was recorded in different Excel sheets; we would open a bunch of sheets and check each patient by name, one by one.”
Today: “No extra calculations to enter, you don't deal with extra numbers.”
Vatanmed
Before the setup: “Each branch kept its own records and the same patient's data lived in different places.”
Today: “The question of what a patient experienced at which branch is now answered by the system itself, not by phone traffic.”
Hairtime Istanbul
Before the setup: “Because data was kept in more than one system, it was hard to see the full picture.”
Today: “We went from being a company that merely uses Zoho CRM to an organization that manages its processes with technology.”
Drag the divider; before on the left, today on the right.
A setup example: AEC Akademi moved its sales process from Excel spreadsheets to a single Zoho CRM dashboard before its growth phase.
1
Live training
At the same table as your team in Istanbul, remotely in other cities and abroad; with real data.
2
Full documentation
Every structure we build is in your hands, in writing.
3
How-to videos
Watch-and-apply recordings for every screen.
4
Fast support
Quick answers to anything left unclear after training.
5
Adoption report
Is the team actually using the system? We measure it.
Every company whose setup we did gets base support through three channels after go-live; it is part of our responsibility and is not priced separately. The WhatsApp channel and phone stay open for as long as we are your partner; feature and customization requests by email in the first 6 months are part of the setup, while new modules and integrations are priced separately.
01 · Email
Feature and customization requests
First 6 months after go-live, for your existing setup. Write to us; the request is logged and planned.
02 · WhatsApp channel
Team questions and instant fixes
A channel set up for your company, open for as long as we are your partner. Your team asks, small fixes happen on the spot.
03 · Phone
Urgent issues and management questions
Open for as long as we are your partner. When something stops work or management needs an answer, call us directly.
Coverage
WhatsApp channel and phone
Email · features and customization
After go-live, for every company whose setup we did. None of the three channels is priced separately; the 6-month scope covers feature and customization requests.
We build it, improve it, keep it alive.
No system survives without someone standing behind it. The team that does your Zoho setup is the team that gives support.
If your question is not here, write to us; we reply within 24 hours.
The 20 business days start after scope approval; the go-live date is written into the scope document. For a Zoho CRM setup, by brief we mean: which processes will go into the system, how many users there will be, which data will be migrated, and what the first reports will measure. If we build the brief together, this work happens before scope approval and is not counted in the 20 business days; we tell you clearly at the end of the discovery call how long it will take.
30+
projects
99%
client satisfaction
3 channels
post-implementation support
We prepare a concrete proposal and a live demo based on your current system, your goals, and your timeline. No commitment before the contract.