العربية — This page is not in Arabic yet. Opens the Arabic home page.

Start free trialBook a demo

Browse the documentation

Documentation

All appsHow the apps connectTeam workflowsCompare

Apps

HR ManagementRecruitment (ATS)Payroll & WPSTime & AttendanceAccounting & E-InvoicingCRM & Sales PipelineSales Orders & FulfilmentInventory, Purchasing & WarehousingProcurement & TendersConstruction & ContractingContracts & E-SignatureProducts & Online StorePoint of SaleRentalsSubscriptions & LicensingHelpdesk & TicketingSocial Media SuiteInfluencer Marketing & Campaign ROIProject ManagementActivities WorkspaceDocument ManagementPDF Tools & E-SignatureCorrespondence RegisterTeam Chat & CallsMeetings & VideoLearning & Certification (LMS)Asset ManagementFleet ManagementRecognition & GamificationContacts & PartnersNotification CentreReports & DashboardsInsights — Business Intelligence & AppsAI CopilotAI Agents & AutomationAI Diagram StudioWebsite BuilderISO Compliance Suite (Imtithal)App MarketplaceCustomer & Partner PortalSecurity, Access & Compliance

CRM Administrator — CRM guide

Set the selling rules once, so nobody has to remember them.

Sets the rules everyone else sells inside: the pipeline and its stages, the fields on a record, where a new lead lands and what it scores, which discounts need signing off, and who is on which team and territory.

What you will be able to do

  • Shape the pipeline and what each stage means
  • Decide where a new lead lands and what it is worth
  • Set the discount that needs a signature
  • Keep teams, territories and the catalogue in order

What this role can and cannot do

CanCannot
  • crm:pipeline:configure
  • crm:custom_field:configure
  • crm:routing_rule:manage
  • crm:lead_score:manage
  • crm:approval:configure
  • crm:lost_reason:configure
  • crm:team:manage
  • crm:territories:write
  • crm:workflow:configure
  • crm:quote_template:manage
  • tenant:settings:write

19 steps, each one carried out in the product on .

Shape the pipeline and its stages #

Where CRM Admin » Pipelines

  1. Open the pipelines configuration screen.
  2. Click the arrow at the left of a pipeline to open its stages.
  3. Use the up and down arrows on a stage to move it.
  4. Click Edit on a stage to change what it means.
What each field wants
FieldWhat to put in it
NameWhat a rep would call this step out loud — Demo, Proposal, Negotiation. Short.
Win probability (%)How often a deal at this stage actually closes. Be honest: this number IS the weighted forecast.
SLA hoursHow long a deal may sit here before it is stale. Leave it blank if you are not measuring that yet.
Closed WonTick for the one stage that means the deal is won.
Closed LostTick for the one stage that means it is lost.
Screenshot: Shape the pipeline and its stages, CRM Administrator view
Each stage row shows its name, its win probability, and a Won or Lost badge if it is one of the two closing stages.

You should see Each stage carries a name, a win probability and whether it counts as won or lost — which is what makes the forecast add up.

Watch out Changing a stage's win probability changes every forecast that includes a deal sitting in it — including the one your board saw last week. Make the change at the start of a period, not the middle. The six configuration screens are not in the left menu. Reach them from the address bar, or press the search key and start typing the name.

Worth knowing This screen is not in the left menu. Type its address, or use the search box at the top and start typing the name.

Add the fields your business actually needs #

Where CRM Admin » Custom fields

  1. Open the custom-fields screen.
  2. Choose the record type at the top: Lead, Contact, Account, Opportunity.
  3. Read the existing fields before adding one — the thing you want may be there already.
Screenshot: Add the fields your business actually needs, CRM Administrator view
Each row shows the key the field is stored under and the label people read, plus a Required badge where one is set.

You should see Anything the product did not ship with — a licence number, a fleet size, a regulator reference — lives here rather than in the description box.

Watch out A field on Lead is not a field on Opportunity. If you want the answer to survive a conversion, add it to both.

Add a field to a record type #

Where CRM Admin » Custom fields » New field

  1. Choose the record type first.
  2. Click New field.
  3. Fill the key and the label, then save.
What each field wants
FieldWhat to put in it
Field keylower case, words joined by underscores, no spaces — trade_licence_no. This never changes.
LabelWhat people see on the form. Change this whenever the wording needs improving.
Screenshot: Add a field to a record type, CRM Administrator view
The key hint under the box says snake_case and immutable — that is the product telling you it cannot be renamed later.

You should see The key never changes once the field exists, so a report written against it keeps working. The label can be reworded whenever you like.

Watch out Pick the key carefully. Everything written against it later — reports, imports, integrations — uses the key, not the label.

Worth knowing Write the key in lower case with underscores — trade_licence_no, not 'Trade Licence No'. It is the name the machine uses, not the one people read.

Decide where a new lead lands #

Where CRM Admin » Lead routing

  1. Open the lead-routing screen.
  2. Read the rules from the top down.
  3. Use the arrows to move a rule up or down.
  4. Switch a rule off rather than deleting it while you are testing.
What each field wants
FieldWhat to put in it
NameWhat the rule does, in words — 'UAE enterprise to the Dubai team'.
StrategyHow the lead is handed out once the rule matches — evenly round the team, or to one named owner.
PriorityHigher runs first. Leave gaps between numbers so you can insert a rule later without renumbering everything.
Screenshot: Decide where a new lead lands, CRM Administrator view
The Pri column is the order. The first rule whose condition matches is the one that assigns the lead; nothing below it is even looked at.

You should see A lead is assigned by rule, not by whoever notices it first — so nobody has to police the queue.

Watch out A rule that matches everything must be last. Put it anywhere else and every rule beneath it is dead — and nothing warns you, because nothing is broken.

Worth knowing Order is the policy. A broad rule sitting above a specific one will swallow every lead the specific one was written for.

Decide what a lead is worth #

Where CRM Admin » Lead scoring

  1. Open the lead-scoring screen.
  2. Read each rule's points.
  3. Use Deactivate to try the model without a rule before deleting it.
What each field wants
FieldWhat to put in it
NameThe signal, in words — 'Opened three e-mails', 'Company over 500 people'.
Score deltaPoints added, or a negative number to take points away.
Screenshot: Decide what a lead is worth, CRM Administrator view
Rules are grouped into demographic — who they are — and behavioural — what they did. A score is the two added together.

You should see The score a rep sees on a lead is the sum of these rules. There is no hidden part to it.

Watch out Scores only mean something relative to each other. Adding a rule worth 200 points makes every other rule irrelevant.

Set the discount that needs a signature #

Where CRM Admin » Approval matrix

  1. Open the approval-matrix screen.
  2. Read each row as one sentence.
  3. Click Add threshold to add a tier.
What each field wants
FieldWhat to put in it
DimensionWhat is being measured — the discount percentage, most often.
Threshold valueThe number above which approval is required. At or below it, the quote goes out on its own.
Approver roleWho has to decide. Choose the role, not a person — people go on holiday.
Pipeline (optional)Leave blank for a rule that covers every pipeline.
Screenshot: Set the discount that needs a signature, CRM Administrator view
A row reads: this measure, above this value, requires this role. A blank pipeline means it applies to all of them.

You should see A quote whose discount goes past the lowest threshold here cannot be sent until somebody with the named role has decided on it.

Watch out The LOWEST discount threshold you set here is the gate. A quote above it cannot be sent until it has been approved, and the send button says so.

Worth knowing Lower the threshold and more quotes stop for a signature; raise it and fewer do. It takes effect on the next quote, not on ones already sent.

Fix the list of reasons a deal is lost #

Where CRM Admin » Lost reasons

  1. Open the lost-reasons screen.
  2. Add the reasons your business really loses on.
  3. Deactivate anything nobody is choosing.
Screenshot: Fix the list of reasons a deal is lost, CRM Administrator view
Active reasons are the ones a rep is offered. A deactivated one stays on the deals that already used it, so your history does not change.

You should see A short fixed list is what makes 'why we lose' a number at the end of the quarter instead of forty different sentences.

Watch out Do not include 'Other'. Everything ends up in it, and then you know nothing.

Add a reason a deal can be lost #

Where CRM Admin » Lost reasons » Add reason

  1. Click Add reason.
  2. Type it and save.
Screenshot: Add a reason a deal can be lost, CRM Administrator view
The new reason appears in the list, active, and is offered on the next deal somebody marks lost.

You should see Short and few. A list of twenty reasons is a list nobody reads to the bottom of, so everything ends up under the first plausible one.

Watch out Write it as a rep would say it out loud — 'Price', 'Went with incumbent', 'No budget this year'. Not a category name.

Keep teams and territories straight #

Where CRM » Teams, and CRM » Territories

  1. Open Sales teams and expand a team to see its members.
  2. Then open Territories and read the priority beside each one.
Screenshot: Keep teams and territories straight, CRM Administrator view
A team is a list of people. A territory is a rule about records. The two often line up, but they are set separately and they can differ.

You should see Team decides whose deals a manager can see. Territory decides where a new record is sent. They answer different questions — do not use one for the other.

Watch out Adding somebody to a team changes what their manager can see. Adding a territory changes where new records go. Doing one and forgetting the other is the usual cause of 'I cannot see my own rep's deals'.

Check the territory rules before a real record hits them #

Where CRM » Territories

  1. Open Territories.
  2. Click Audit expressions to check every rule at once.
  3. Read the report: rules that cannot be understood, and rules that can never match because something above them always does.
Screenshot: Check the territory rules before a real record hits them, CRM Administrator view
The report counts how many territories were checked and how many have a problem, then names each one.

You should see A rule that cannot be understood, or one sitting underneath a catch-all that will always match first, is named — before a lead disappears into it.

Watch out A shadowed rule is not an error — nothing is broken and nothing warns you. It simply never fires, and the leads it was written for go somewhere else.

Worth knowing A rule of just 'true' matches everything. Anything below it is dead, and the check is what tells you.

Build the forms that bring leads in #

Where CRM » Lead Forms

  1. In the left menu, click Lead Forms.
  2. Open a form to see the fields it asks for.
  3. Use the embed option and give the code to whoever looks after the website.
Screenshot: Build the forms that bring leads in, CRM Administrator view
Each form shows what it collects and how many people have completed it, so a form nobody finishes is obvious.

You should see A lead that arrives from a form is complete and goes straight to the routing rules — nobody re-types an enquiry out of an inbox.

Watch out Every extra box on a form costs you leads. Ask for the two or three things you cannot start without, and get the rest on the first call.

Worth knowing Ask for as few fields as you can live with. Every extra box costs you leads, and most of what you want can be asked on the first call.

Keep the catalogue and its prices in order #

Where CRM » Products, and CRM » Price lists (both open the catalogue)

  1. Open Products and read the categories.
  2. Then open Price lists.
  3. Open a list to see its rules: what sets a price, for which product, from how many units.
Screenshot: Keep the catalogue and its prices in order, CRM Administrator view
A product is what you sell. A price list is what it costs, and there can be more than one — retail, partner, a regional list.

You should see A rep puts a product on a quote and the price comes from the list. Nobody types a price from memory.

Watch out Archive a product rather than deleting it. Deals and quotes that already reference it must keep working.

Let customers book their own time #

Where CRM » Booking Pages

  1. In the left menu, click Booking Pages.
  2. Open a page to see its title, who it books with, and the slot length.
  3. Copy its link and put it in the team's e-mail signature.
What each field wants
FieldWhat to put in it
Page titleWhat the customer reads at the top — 'Book a 30-minute demo'. Not the internal name.
Screenshot: Let customers book their own time, CRM Administrator view
Each page carries an active badge and the link customers use.

You should see A slot somebody books becomes a meeting on the right record. The back-and-forth about times never reaches anybody's inbox.

Watch out A booking page pointing at somebody who has left keeps taking bookings. Deactivate it the day they go, not the day somebody notices.

Tidy a batch of records at once #

Where CRM » Leads

  1. Open Leads.
  2. Tick the rows you want to deal with — or tick the header box to take everything currently on screen.
  3. Use the bar that appears at the bottom.
Screenshot: Tidy a batch of records at once, CRM Administrator view
The bar counts your selection and shows only the actions your sign-in allows.

You should see Removing records in a batch is offered to this role and to nobody who sells — which is what stops a bad afternoon becoming a lost quarter.

Watch out Filter FIRST, then tick the header box. It selects the rows you are looking at, and the rows you are looking at are whatever the filter left.

See the whole company's book #

Where CRM » Leads, and CRM » Opportunities

  1. Open Leads and read the count in the line under the title.
  2. Open Opportunities and read the same line.
Screenshot: See the whole company's book, CRM Administrator view
The subtitle carries the count. This sign-in is not scoped to an owner, so these are the company's numbers.

You should see You are not scoped to an owner. These two numbers are the whole company's, which is why a rep's shorter list is proof that ownership is working rather than proof that something is missing.

Watch out These two numbers are the yardstick. When a rep tells you records are missing, compare their count with yours before assuming anything is broken — a smaller list is the system working.

Salaries are not yours to see #

Where The left menu

  1. Open the launcher and read the tiles.
  2. Payroll is not among them for this sign-in.
Screenshot: Salaries are not yours to see, CRM Administrator view
The launcher shows only the apps your sign-in can open.

You should see Setting up how the company sells is not a reason to see what anybody is paid, so the whole area is closed rather than merely hidden.

Watch out This is a refusal, not a hidden menu. Typing the address gets the same answer.

Refresh the forecast for a team or a territory #

Where CRM » Forecasts » Forecast for

  1. Open Forecasts; the current quarter is selected.
  2. In Forecast for, choose the whole company, one team or one territory (territories are listed when Territories is switched on and you can read them).
  3. Press Refresh: a new snapshot for that subject joins the list, and the tiles add each deal once — the newest snapshot per subject, never every refresh.
Screenshot: Refresh the forecast for a team or a territory, CRM Administrator view
A territory's forecast is its accounts' open deals plus its sub-territories', weighted by each deal's win probability, in the company currency.

You should see A territory's forecast is its accounts' open deals plus its sub-territories', weighted by each deal's win probability, in the company currency.

Set how a quote looks #

Where CRM » Quote templates

  1. Open CRM » Quote templates.
  2. New quote template; name, language, opening text, terms; Save.
Screenshot: Set how a quote looks, CRM Administrator view
The list of templates and the template form.

You should see On a quote, the rep picks the template beside Send; the printed quote can be saved as a PDF to Documents.

Watch out Reps pick a template on the quote; a change here applies to quotes sent afterwards.

See who filled in a lead form and what became of it #

Where CRM » Lead Forms » a form » Submissions

  1. Open CRM » Lead Forms.
  2. Open a form's Submissions.
  3. Open the lead, or press Retry on a failed row.
Screenshot: See who filled in a lead form and what became of it, CRM Administrator view
Everyone who filled in the form with their status and the lead each one became.

You should see Each submission shows its status and links to the lead it created.

Watch out Someone already in CRM gets a note on their lead, not a second lead. Retry is shown only for failures.

Use cases — the work, step by step

Each one is a sequence somebody actually performs, with the screen behind every step. Every screen here was opened in the product as this role before it was published.

edgeStand up a sales process before the team touches it #

Stages, reasons and thresholds are cheap to change on day one and expensive on day ninety — every deal already in flight carries whatever you chose.

  1. Build the pipeline and its stages first. Be honest about the win probabilities: that number IS the weighted forecast everybody will later argue about.

    CRM Administrator doing "Stand up a sales process before the team touches it" in Tarleaks ERP — Build the pipeline and its stages first. Be honest about the
    CRM Admin » Pipelines — verified: the page says “Pipeline”
  2. Set the lost reasons. Short, specific, and no 'Other' — everything ends up in Other and then you know nothing.

    CRM Administrator doing "Stand up a sales process before the team touches it" in Tarleaks ERP — Set the lost reasons. Short, specific, and no 'Other' — ever
    CRM Admin » Lost reasons — verified: the page says “Lost Reasons”
  3. Set the discount thresholds. The lowest one you configure is the gate: a quote above it cannot be sent until somebody decides.

    CRM Administrator doing "Stand up a sales process before the team touches it" in Tarleaks ERP — Set the discount thresholds. The lowest one you configure is
    CRM Admin » Approval matrix — verified: the page says “Approval Matrix”
  4. Add the fields your business actually asks about, per record type. A field on Lead is not a field on Opportunity — add it to both if the answer must survive a conversion.

    CRM Administrator doing "Stand up a sales process before the team touches it" in Tarleaks ERP — Add the fields your business actually asks about, per record
    CRM Admin » Custom fields — verified: the page says “Custom Fields”

monthlyA new region opens: staff it, route to it, score for it #

Team and territory answer different questions. Doing one and forgetting the other is the usual cause of 'I cannot see my own rep's deals'.

  1. Create the team and put the people in it. Team membership is what makes a manager's team-wide pipeline mean the right set of deals.

    CRM Administrator doing "A new region opens: staff it, route to it, score for it" in Tarleaks ERP — Create the team and put the people in it. Team membership is
    CRM » Teams, and CRM » Territories — verified: the page says “Sales teams”
  2. Add the territory and give it a priority. Priority decides which territory claims a record when more than one could.

    CRM Administrator doing "A new region opens: staff it, route to it, score for it" in Tarleaks ERP — Add the territory and give it a priority. Priority decides w
    CRM » Teams, and CRM » Territories — verified: the page says “Sales teams”
  3. Run the audit over every territory rule. A rule sitting under an earlier catch-all never fires, nothing is broken, and nothing warns you — the audit is what tells you.

    CRM Administrator doing "A new region opens: staff it, route to it, score for it" in Tarleaks ERP — Run the audit over every territory rule. A rule sitting unde
    CRM » Territories — verified: the control is offered
  4. Add the routing rule that sends the region's leads to the new team, and put it above the general one. Order is the policy.

    CRM Administrator doing "A new region opens: staff it, route to it, score for it" in Tarleaks ERP — Add the routing rule that sends the region's leads to the ne
    CRM Admin » Lead routing — verified: the page says “Lead Routing”
  5. Adjust the scoring if the new market qualifies differently. Deactivate a rule to try the model without it before deleting it.

    CRM Administrator doing "A new region opens: staff it, route to it, score for it" in Tarleaks ERP — Adjust the scoring if the new market qualifies differently.
    CRM Admin » Lead scoring — verified: the page says “Lead Scoring”

urgentReps say their leads are going to the wrong people #

It is almost always the rule ORDER rather than a broken rule, and nothing errors when the order is wrong.

  1. Open Lead Routing and read from the top. The first rule that matches assigns the lead and nothing below it is even looked at.

    CRM Administrator doing "Reps say their leads are going to the wrong people" in Tarleaks ERP — Open Lead Routing and read from the top. The first rule that
    CRM Admin » Lead routing — verified: the page says “Lead Routing”
  2. Look for a broad rule sitting above a specific one. That is the fault nine times in ten, and it is invisible until somebody complains.

    CRM Administrator doing "Reps say their leads are going to the wrong people" in Tarleaks ERP — Look for a broad rule sitting above a specific one. That is
    CRM Admin » Lead routing — verified: the page says “Lead Routing”
  3. Run the territory audit as well — a shadowed territory produces exactly the same symptom from the other direction.

    CRM Administrator doing "Reps say their leads are going to the wrong people" in Tarleaks ERP — Run the territory audit as well — a shadowed territory produ
    CRM » Territories — verified: the control is offered
  4. Check the team membership last. A rep who was never added to the team gets the leads and their manager still cannot see them.

    CRM Administrator doing "Reps say their leads are going to the wrong people" in Tarleaks ERP — Check the team membership last. A rep who was never added to
    CRM » Teams, and CRM » Territories — verified: the page says “Sales teams”

weeklyMarketing wants a form on the website by Friday #

A form that captures leads nobody is routed is a form that produces an unworked queue. Build the form and the route in the same sitting.

  1. Build the form. Ask for the fewest fields you can live with — every extra box costs leads, and the rest can be asked on the first call.

    CRM Administrator doing "Marketing wants a form on the website by Friday" in Tarleaks ERP — Build the form. Ask for the fewest fields you can live with
    CRM » Lead Forms — verified: the page says “Lead Capture Forms”
  2. Make sure a routing rule covers what the form will produce, before the code goes on the website rather than after.

    CRM Administrator doing "Marketing wants a form on the website by Friday" in Tarleaks ERP — Make sure a routing rule covers what the form will produce,
    CRM Admin » Lead routing — verified: the page says “Lead Routing”
  3. Publish a booking page alongside it where a demo is the obvious next step. A booked slot becomes a meeting on the right record with no e-mails about times.

    CRM Administrator doing "Marketing wants a form on the website by Friday" in Tarleaks ERP — Publish a booking page alongside it where a demo is the obvi
    CRM » Booking Pages — verified: the page says “Booking Pages”
  4. Watch the leads land on the list for a day before you tell marketing it is live.

    CRM Administrator doing "Marketing wants a form on the website by Friday" in Tarleaks ERP — Watch the leads land on the list for a day before you tell m
    CRM » Leads, and CRM » Opportunities — verified: the page says “Opportunities”; 25 row(s) listed

You do not sell, and you do not approve deals. What you do is decide the shape of the process — which is why a change you make here changes what every other person in this guide sees.

All crm role guides

Last updated