DOCS / SUPPORT CONSOLE / SETUP

MERCHANT GUIDE · SETTINGS REFERENCE

Set up your helpdesk, step by step

Every tab under Settings in the support console, one task at a time: adding team members and queues, tiers and roles, response targets and business hours, channels and email, saved replies, labels, fields, forms, automation, campaigns, calls and developer tools. To work cases day to day, read the Support console guide.

Places are written as Codexta › Support console › Inbox. In Shopify, Codexta is under Shopify admin › Apps › Codexta; in WooCommerce, under WooCommerce › Codexta Assistant. Things you can type look like “I want to talk to a real person”. Back to the Shopify guide or the WooCommerce guide. New words are explained in the glossary.

ON THIS PAGE
01

Before you start

This page is the step-by-step reference for everything under Settings in the support console. For day-to-day work (answering chats, tickets, contacts, reports) see the Support console guide.

Where are the settings and what is on each tab?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings

Only the Owner and Admins see Settings. Everyone else who opens it reads You don’t have access to helpdesk settings. The page says How the helpdesk routes and times cases. Changes apply to new activity right away. The tabs, in the order you see them:

TabWhat it controlsSteps
QueuesTeams that work cases, and how new cases are shared out.Queues
TiersSupport levels for escalation.Tiers
PrioritiesPriority names and their response targets.Priorities
SLA policiesTargets that depend on queue, channel, label or priority.SLA policies
Business hoursWeekly hours, holidays, time zone.Business hours
Live chatWhen people take new chats, and a temporary pause.Live chat
MembersWho works which queue at which tier.Members
RolesCustom roles that limit what an agent sees or does.Roles
ChannelsWhere cases come in: email, live chat, your own app.Channels
EmailYour own mail server and the branded email layout.Email
BackendsSwitches for tickets, live chat and email intake.Switch the helpdesk on
Saved repliesReady-made answers agents insert with /.Saved replies
LabelsColoured tags and sidebar lists.Labels
FormsContact, wholesale and return forms for your store.Forms
AttributesYour own fields on cases and contacts.Attributes
CampaignsWidget messages and one-off SMS.Campaigns
MonitorsPlain-English checks on resolved cases.Monitors
AutomationRules that act on cases by themselves.Automation
MacrosSeveral actions in one click.Macros
WebhooksSigned messages to your server.Webhooks
Agent botsYour own bot takes a channel’s new cases first.Agent bots
Dashboard appsYour own page as a tab beside every case.Dashboard apps
AppsSlack, Linear, Stripe, Notion.Slack and other apps
CallsPhone calls to your Twilio number.Calls
Data & auditErase a customer, audit log, import, sign-in rule.Data and audit

How do the settings lists behave?

  • In Queues, Tiers, Priorities, Business hours, Members and Channels, press the Add … button above the list to make a new row. Click a row to open it. Press Save to keep your changes.
  • The Code of a queue, tier, priority, business hours or channel is its key. It cannot be changed later, so pick it with care. Queue, tier, business hours and channel codes are stored in capitals, priority codes in lower case.
  • These rows are never deleted. Press Deactivate to retire one and Reactivate to bring it back. Show inactive above the list shows the retired rows. Cases already on a retired row keep it.
  • Saved replies, labels, attributes, SLA policies, rules, macros, webhooks, bots, dashboard apps and forms use a small list with a pencil (edit) and a bin (delete). Deleting asks you to confirm first.
  • Changes apply to new activity right away. Cases already open keep the due times they have.

Example: set up a small helpdesk in the right order

  • Who: Owner, Admin
  • Plan: any

A new shop already has a Support queue, two tiers and four priorities (see what is set up). A sensible order for the rest:

  1. Business hours: set your real opening hours and time zone.
  2. Queues: choose those hours on the Support queue, and add a Billing queue if you want one.
  3. Priorities: check the response targets match what you promise.
  4. Members: add your colleagues to their queues.
  5. Live chat and Backends: switch on what you offer.
  6. Saved replies and labels: write the five answers you give most often.
  7. Contact options: add your WhatsApp, Viber and phone number so shoppers have a way in when the assistant cannot help.
  8. Send yourself a test: open your shop chat, type “I want to talk to a real person” and answer it from the Inbox.
02

People: members, roles, availability and capacity

How do I add a team member to a queue?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Members

A member is one person in one queue at one tier. The same person can have a place in several queues. First give the person a role in Codexta’s Settings › Team (Support agent or Support manager; see the Shopify or WooCommerce guide). Owners, Admins, Support managers and Support agents can be picked here.

  1. Press Add member. The sheet says Gives a Codexta account a place in a queue at a tier.
  2. Team member: open Pick a team member and choose the person. The list shows your store’s owners, admins and support agents with their email and role.
  3. Queue: choose one queue, or All queues to make them a member everywhere. If the person already has a place in that queue, saving updates it instead of adding a second one.
  4. Tier: choose their level. The hint reads They can own cases at rank {n} or lower.
  5. Display name (optional): how they appear in the Inbox and, with the Friendly setting, in shoppers’ chats. It defaults to the name on their Codexta account.
  6. Role: leave Built-in agent role, or pick a custom role. This field only appears once you have made a custom role.
  7. Tick Reviews new requests if they should get an email for every new ticket in that queue (or in any queue, if you chose All queues). Only members you tick here are emailed.
  8. Press Save.

The list shows Person, Queue, Tier and New requests (Emailed when ticked). Use the Every queue menu to look at one queue; that view includes the All queues members.

Example. Ana helps with money questions. Add her twice: Support at tier Support, and Billing at tier Tier 2. She now takes first-line cases in Support and escalated cases in Billing.

To change someone’s tier, display name, role or the review box, click their row. Their email and queue are fixed; to move them, add them to the new queue and deactivate the old row. Deactivate says They can no longer own cases through this membership. and Reactivate brings it back.

How do I make a custom role?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Roles

A role narrows what an agent may do, instead of the built-in agent role. Admins are never limited by one.

  1. Press Add role.
  2. Fill in Name and, if you like, Description.
  3. Under Cases, choose one:
    • Every case of their queues (the starting choice).
    • Unassigned cases and their own.
    • Only their own and those they take part in.
  4. Under Also, tick what they may do: Manage contacts, See reports, Manage the help center.
  5. Press Save role (Cancel drops it).
  6. Give the role to a person: Settings › Members, open their row, Role.

To change a role, click it in the list. The bin deletes it after Delete the role {name}? Its members get the built-in agent role. With no roles at all the list says No roles yet: agents have the built-in agent role.

How do availability and capacity work?

  • Availability. Everybody sets My availability to Online, Busy or Offline at the top of the console. While the console is open it tells Codexta every minute that you are still there. A queue that assigns automatically gives new cases only to people who are online with their console open.
  • Capacity. In a queue, At most open cases per member stops a person getting more cases while they hold that many. Empty means no limit. Fair distribution adds a rate limit: at most that many automatically assigned cases per person in the minutes you give. See queues.
  • Tier. Automatic assignment goes to a member at the case’s tier or above.
03

Queues and tiers

How do I create a queue?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Queues

The sheet says Cases are routed to a queue; members of the queue work them.

  1. Press Add queue.
  2. Code: the key, for example BILLING. It is stored in capitals and cannot be changed later.
  3. Name: shown in the Inbox and on cases. It defaults to the code.
  4. Icon and colour and Description are optional. No colour clears the colour.
  5. Business hours: choose a set of hours, or 24×7 (no business hours). Response targets of this queue count only inside these hours.
  6. Auto-escalate on SLA breach: when a case misses its target it moves to the next tier up and loses its owner.
  7. Ask for a satisfaction rating (CSAT): see ratings.
  8. Auto-resolve after: a new, open or pending case with no activity for this long is resolved. Choose an amount and a unit (days, hours or minutes), at least 10 minutes. Empty means never. Once you set it, three more fields appear:
    • Auto-resolve message (optional): sent to the customer as a reply.
    • Auto-resolve label (optional): a tag put on those cases.
    • Never auto-resolve a case waiting on an agent: a case whose last public message is the customer’s is left alone.
  9. Assign new cases automatically: new cases (and cases that lose their owner) go to a member who is online, at the case’s tier or above. Then choose How:
    • Round robin (whoever waited longest).
    • Balanced (fewest open cases).
    Optionally set At most open cases per member and Fair distribution (a number of cases per a number of minutes).
  10. Sort order: lower numbers come first in lists.
  11. Default queue: cases created without a queue land here. Exactly one queue is the default; to change it, open the queue you want and tick this box. The old default stops being the default.
  12. Press Save.

The list shows Queue, Default, Business hours, Auto-escalate and Members (active members, including All queues members). Deactivate says New cases can no longer be routed to it; its existing cases stay where they are. The default queue cannot be deactivated.

Example. Billing: code BILLING, business hours Office, Assign new cases automatically on with Balanced (fewest open cases), At most open cases per member 15. Then build a rule that moves invoice questions there (automation).

Which queue does a new case get? That of the channel it came in on, else the default queue. A rule or a person can move it with Move to queue….

How do I add a tier and use escalation?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Tiers

A tier is a support level, such as first line or specialists. A member at a tier may own cases at that tier or any lower rank. Escalating moves a case up to the next active tier by rank.

  1. Press Add tier.
  2. Code (for example L3; stored in capitals, fixed later) and Name (defaults to the code).
  3. Rank: a whole number, 1 or higher. Higher is more senior. Each tier needs its own rank; the sheet tells you if one is used.
  4. Press Save.

The list shows Rank, Tier and Members (active memberships at that tier). Deactivate says Cases already on this tier keep it; escalation skips it from now on.

How cases move. In a case’s details, Escalate asks Why escalate to the next tier? and moves the case up one tier. De-escalate moves it back down. A queue’s Auto-escalate on SLA breach does the same by itself. A rule can use the action Escalate a tier.

04

Priorities, response targets and business hours

How do response targets fit together?

A response target (SLA) is how fast you promise to answer. Each case gets its due times from, in this order: the first SLA policy whose conditions match, else the targets of its priority. All targets count inside the queue’s business hours (around the clock if the queue has none). A case shows First response due, Next response due and Resolution due, and SLA breached when one is missed. While a case is pending the clock stops (SLA paused while pending, since).

How do I add or change a priority?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Priorities

  1. Press Add priority. The sheet says A priority sets the SLA targets of its cases.
  2. Code (stored in lower case, for example critical) and Name.
  3. Rank: a whole number. Higher is more urgent.
  4. First response target: time to the first agent reply. Resolution target: time to resolve. Give each an amount and a unit (days, hours or minutes); it must come to whole minutes.
  5. Default priority: new cases without a priority get this one. Exactly one is the default.
  6. Press Save.

The list shows Priority, Rank, First response, Resolution and Default. Deactivate: new cases can no longer use it; cases that have it keep it.

How do I make an SLA policy for some cases only?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › SLA policies

The first active policy (in order) whose conditions match sets a case’s targets. Cases no policy matches keep their priority’s targets.

  1. Press Add.
  2. Name and Order (lower numbers are checked first). Description is optional.
  3. Conditions: Queue, Channel, Label and Priority. Each is Any or one choice. A policy with no condition fits every case.
  4. Targets: First response, Next response and Resolution. Empty means no target. Next response runs from a customer’s message, after the first answer, to the next reply. You need at least one target.
  5. Tick Only during the queue’s business hours to count only open hours; otherwise the policy runs around the clock.
  6. Keep Active ticked and press Save.

Example. Cases with the label vip get a first response in 15 minutes: Name VIP, Label vip, First response 15 minutes. A rule can also apply a policy by name with the action Apply an SLA policy. Deleting a policy asks Delete the SLA policy “{name}”? Cases keep their current due times.

How do I set business hours and holidays?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Business hours

  1. Press Add business hours (or click existing hours).
  2. Code (for example EU_OFFICE, stored in capitals, fixed later) and Name.
  3. Time zone: set it first. The weekly hours and the holidays are in this zone.
  4. Weekly hours: tick each open day. A new day opens 09:00–17:00. Edit the two times (HH:mm, 24:00 means midnight at the end of the day), press Add window for a second window such as 13:00–17:00, and the cross to remove one. The end must be after the start. Open at least one day.
  5. Holidays: pick a date and press Add. Click the cross on a date to remove it. On a holiday the SLA clock does not run and live chat stays closed.
  6. Press Save.

The list shows Business hours, Open (a summary such as Mon–Fri 08:00–17:00), Holidays and Used by (the queues). Choose the hours on a queue so its targets count only while open. Live chat, campaigns and calls can follow them too.

05

Live chat and the switches

How do I decide when live chat is open?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Live chat

The tab starts with a line such as Live chat is open or closed, and why.

  1. Under the heading Live chat hours choose how live chat works:
    • Always open: People can ask for a person at any time.
    • Follow business hours: only while the hours are open; every weekday has its own times and holidays are closed.
    • Off: nobody can start a live chat; the assistant takes a ticket instead.
  2. With Follow business hours, pick which hours under Live chat hours, or keep The default queue’s hours. The times themselves are in Business hours. If no hours are found, live chat stays open.
  3. Each change is saved when you make it.

To pause for a while, use Pause live chat for a while: 30 minutes, 1 hour, Until tomorrow, or pick a time and press Pause until. The pause ends by itself and beats the hours. Resume now ends it early. A chat already open is never cut off.

Chats go to the first active Live chat channel (the list says Takes new live chats). See channels.

What do the Backends switches do?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Backends

Three built-in helpdesk features, each with an On or Off button that applies in a few seconds and to your store only: Tickets and incident reports, Live chat with a person and Email intake (add an email channel and its mailbox secret first). Details: switch the helpdesk on.

06

Channels and email

What is a channel and how do I add one?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Channels

A channel is a way cases come in. Each routes its new cases to a queue, with a starting priority and tags. The console offers three kinds: Email (a mailbox the email intake reads), Live chat (chats handed over from the assistant) and API (your own app). Messaging apps such as Instagram, WhatsApp or Telegram are connected in Codexta’s own Settings › Integrations page (title “Connect”), not here; see the Shopify or WooCommerce guide.

  1. Press Add channel. The sheet says Where cases come in, and where they are routed.
  2. Choose the Kind. It cannot be changed later.
  3. Fill in Code (stored in capitals, fixed later; for example BILLING_MAIL or WEBCHAT) and Name.
  4. Fill in the fields of the kind (below).
  5. Queue: where new cases land (Default queue if you leave it). Replies stay with their case.
  6. Priority: the priority new cases start with. Tags: comma-separated; added to every new case from this channel. Sort order: lower first.
  7. Press Save.

The list has Search channels and shows Channel, Queue, Priority and Tags. A channel with a broken connection shows Reconnect needed: and the reason. Deactivate stops it; its existing cases stay where they are.

Email channel. Address is the public address (mail from it is ignored as your own). Mailbox secret names the mailbox connection Codexta keeps for you; only its name is stored. We set that up for you (see email intake). When a Forwarding address is shown, you can forward your support address to it in your mail provider instead; replies still leave from the mailbox.

Live chat channel. Agent name in the chat: Friendly (the agent’s name) or Professional (no personal name). Optionally pick an Agent bot (see bots); None: people answer is the default. Live chats go to the first active live chat channel.

API channel. For a developer. After saving, the sheet shows the Client API address and the HMAC token. Set the Callback URL (https) where agent replies and case changes are sent. Make a new token on save (the old one stops working) replaces the token. Tick Require an identifier hash for new contacts (HMAC) when the contacts are your signed-in users, so nobody can pose as one of them.

How do I set the email server and the email layout?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Email

This is the server your helpdesk sends from: the “we have your request” email, the new-ticket email to members who review new requests, and your replies. Without one, the platform’s mail server sends them. The tab says which one is in use (Sending from).

  1. SMTP server (for example smtp.office365.com), Port (587 for most), Username (usually the mailbox address) and Password. Once saved, the password is kept; leave it empty to keep it.
  2. From address: customers see it and reply to it. From name (optional): for example your store’s name.
  3. Keep Encrypted connection (TLS) ticked unless your provider says otherwise.
  4. Press Save, then type an address in Send a test to (empty: your own email) and press Test. You read Test email sent. Check the inbox. or Not sent: … with the reason.
  5. To go back, press Use the platform’s mail server.

Branded layout. Tick Use the branded layout to put a frame around every email to a customer (the acknowledgement, replies, transcripts and the satisfaction survey): Logo (https address), Brand colour, Header text (usually your shop’s name) and Footer (address, opening hours). A preview shows the result. Press Save.

07

Saved replies, labels and attributes

How do I write saved replies?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Saved replies

  1. Press Add.
  2. Short code: letters, digits, - or _. The code is saved in lower case, for example refund.
  3. Text: the answer. You can use {{customer.name}}, {{customer.email}}, {{agent.name}}, {{agent.email}}, {{ticket.number}} and {{ticket.title}}.
  4. Press Save. The pencil edits and the bin deletes (after Delete the saved reply /{code}?).

In a reply, an agent types / and the code, or presses Saved replies in the composer. If a name could not be filled (for example no customer name), the composer warns These variables could not be filled: … and offers Send anyway or Edit. Full example: create a saved reply.

How do I manage labels?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Labels

  1. Press Add.
  2. Title: lower case, at most 50 characters, for example billing. Colour and Description are optional.
  3. Tick Show in the sidebar to get a list of every case with the label under Labels in the Inbox.
  4. Press Save.

Renaming a label renames it on every case. Deleting one (Delete the label “{name}”? It is removed from every case that has it.) removes it from them. Agents add labels to a case under Tags, and Suggest labels lets the AI propose fitting ones. A label can be a condition of an SLA policy or a rule.

How do I add my own fields?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Attributes

  1. Press Add.
  2. Applies to: Cases or Contacts.
  3. Key: letters, digits, - or _ (for example order_number). Type: Text, Number, Currency, Percent, Link, Date, List or Checkbox. Applies to, key and type cannot be changed once saved.
  4. Name: what agents see.
  5. For a list, give Options, one per line. For text you may set a Pattern (optional), a regular expression the whole value must match.
  6. For a case field, tick Required before resolving so nobody resolves a case without it.
  7. Press Save.

Agents fill case fields in the case’s Attributes (press Save attributes); contact fields are on the contact. In the Inbox, Filters has Attribute (key:value). Deleting one says Values already set stop showing.

08

Forms for your store

A form is a contact, wholesale or return form you build in the console and put on a page of your store. Each submission becomes a ticket, labelled with the form’s key and name.

Example: build a return request form

  • Who: Owner, Admin

Codexta › Support console › Settings › Forms

  1. Press New form. The window says Start from a template. Everything can be changed in the builder. Choose Contact us, Wholesale application, Return request, Product quiz (three steps with picture cards and a question only some shoppers see) or Blank. Pick Return request: it has order number, email, name, delivery date, items, reason, what the customer wants and photos.
  2. The builder opens. On the left, Blocks (with Search blocks…) has layout blocks (Heading, Text, Image, Divider, Spacer, Columns, Step) and fields (Text, Email, Phone, Number, Paragraph, Date, Dropdown, Single choice, Checkbox, Multiple choice, File upload). Drag one onto the form.
  3. Click a block to change it in the right-hand panel, tab Block. For a field: Type, Label, Placeholder, Help text, Options (one per line), Show options as List or Cards, Required, Width (Full width or Half width) and Field name (the answer’s name in the ticket). A file field has Accepted files (for example image/*,.pdf; images and PDFs reach the ticket).
  4. To show a field only for some answers, use Show when under the block, with conditions on other fields (All conditions match or Any condition matches), or Show from and Show until dates. Use Step blocks to split a long form into pages.
  5. Open the tab Form. Under Form set Name, Key (lower-case letters, digits and dashes; the embed code and the ticket label use it; it cannot change once the form has submissions) and Accepting submissions. Under After the form set Submit button, for forms with steps Next button and Back button, and Success message (shown with the ticket number). Theme sets colours, Corner radius, Font size, Font, Labels position and the Submit button width. Custom CSS applies only inside this form.
  6. Press the eye button (Try the form as shoppers see it) to test conditions and steps. Nothing is sent. The device buttons preview desktop and mobile width, and Undo and Redo are in the top bar.
  7. Press Save. It will not save until the form has a name, a valid key, an Email field (“so we can reply”), unique field names, and at least one option for every choice field.
  8. Press Embed (available after the first save). Copy the Form key and follow the tab for your platform:
    • Shopify: Online Store › Themes › Customize, open the page, Add block (or Add section › Apps), pick Codexta form, paste the key into Form key and Save.
    • WooCommerce: add the shortcode [codexta_form key="your-key"] to a page (needs the Codexta plugin connected).
    • BigCommerce, Shopware and any website: paste the HTML snippet shown (a div with data-codexta-form and a script). BigCommerce asks for the Store hash, Shopware for the Shop id.

Back in the list, each form has the switch Accepting submissions (On/Off; when off, the storefront says the form is not available), Submissions (opens the cases with that label), Export CSV (every answer in columns; the newest 50,000 submissions at most), the pencil and the bin (Delete the form “{name}”? Its tickets and their label stay.).

09

Automation rules and macros

Example: send invoice questions to Billing

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Automation

When something happens on a case and the conditions match, the actions run on that case. A rule’s own changes never start another rule.

  1. Press Add rule.
  2. Name: Invoices to Billing.
  3. When: A case is created.
  4. If (all cases when empty): press Condition. Choose Title / subject, contains, and the value invoice. Several values separated by commas are alternatives. Between conditions choose and or or.
  5. Then: press Action. Choose Move to queue and pick Billing. Add more actions if you like.
  6. Keep Active ticked and press Save rule (a name and at least one action are needed).

In the list, the tick box switches a rule on or off. Rules are checked every few minutes and run once per case.

PartWhat you can choose
WhenA case is created, A case is changed, A case is (re)opened, A case is resolved, A message is added, and the timed ones The customer has not answered for…, Nobody from the team has answered for… and A case stays in its state for…. A timed trigger has After: an amount in minutes, hours or days. It runs once per case until the case moves on.
If: aboutState, Priority, Queue, Tier, Channel, Source, Kind, Customer email, Title / subject, Tag, Owner email, Message text, Message from (customer / agent / bot), Message is internal (true / false).
If: howis, is not, contains, does not contain, starts with, is set, is not set.
ThenAssign to agent (an email), Remove the owner, Move to queue, Add tags, Remove tags, Set priority, Set state, Resolve, Escalate a tier (with a reason), Send a reply to the customer, Add an internal note, Email the queue’s team, Send a webhook, Apply an SLA policy (by name), Email the transcript (empty address: the customer).

Text actions can use the same names as saved replies, such as {{ticket.number}} and {{customer.name}}.

How do I make a macro?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Macros

  1. Press Add macro.
  2. Name, for example Billing, high priority.
  3. Who can use it: Only me or Everyone.
  4. Under Actions add the steps, from the same list as rules (Add tags billing, Set priority High, Move to queue Billing).
  5. Press Save macro.

Agents run it from a case with Macro… in the case header or Run a macro in the composer, and on many cases at once with Run macro on selected in the bulk bar.

10

Campaigns, monitors and calls

How do I make a campaign?

  • Who: Owner, Admin

Codexta › Support console › Settings › Campaigns

A widget campaign is a message your shop’s chat widget shows above its button after a visitor has been on a matching page for a while. A click opens the chat with the message as its greeting. Each visitor sees a campaign at most once per visit.

  1. Press Add. Choose the Kind: Widget message on your pages or One-off SMS to contacts with a label.
  2. Title (for you only) and Message.
  3. For a widget message: Sender name (optional), Pages (a link or path, * for any text, for example /products/*; empty: every page) and After (seconds on the page) (0 to 3600).
  4. For an SMS: Contacts with the label and Send at (empty: as soon as it is enabled). An SMS needs an SMS number connected in Codexta’s Settings › Integrations. Send due SMS now sends what is due right away.
  5. Tick Only during business hours and choose the hours if you like. Keep Enabled ticked and press Save.

How do I make a monitor?

  • Who: Owner, Admin

Codexta › Support console › Settings › Monitors

  1. Press Add, give it a name, and describe in Look for what to find, in plain English (at least 5 characters): the customer says they will cancel or go to a competitor. Under Tag matching cases you can name a tag to put on matching cases (empty: no tag).
  2. Press Preview on recent cases. Each checked case shows match or no match with the reason. Nothing is saved yet.
  3. Press Save.

The AI checks every resolved case from then on. The list shows how many cases {m} of {n} matched, and opens the matches with the reason. Check past cases runs it on older ones, Pause and Resume stop and restart it. Deleting a monitor keeps the tags it added.

How do I take phone calls?

  • Who: Owner, Admin

Codexta › Support console › Settings › Calls

Calls use the Twilio number you connected for SMS in Codexta’s Settings › Integrations. Without it the tab says Connect a Twilio number first (Connect → SMS); the same number takes calls.

  1. Tick Take calls on this number.
  2. Phones to ring: up to 5 numbers, comma-separated, in international format (for example +38761000111).
  3. Business hours: the phones ring inside these hours (The default queue’s if left). Otherwise, or when nobody answers, the caller leaves a voicemail.
  4. Greeting and Voicemail greeting: what the caller hears (at most 300 characters each).
  5. Tick Record answered calls and Transcribe recordings and voicemails if you want them.
  6. Press Save.

Every call is logged on a case of the caller. The console section Calls lists them: filter by Status (completed, voicemail, no-answer, busy, failed, ringing), see the direction, number, length, agent, a transcript snippet, Recording and the case number. On a case that began as a call, Call the customer asks for your own phone number: Twilio rings you first, then connects you to the customer.

11

Webhooks, bots, dashboard apps and tokens

Most shops do not need these. They are for a developer working with you.

How do I add a webhook?

  • Who: Owner, Admin

Codexta › Support console › Settings › Webhooks

  1. Press Add webhook.
  2. URL: your server’s address, for example https://example.com/hooks/helpdesk.
  3. Tick the Events: Case created, Case changed, Case (re)opened, Case resolved, Message added, Satisfaction rating. At least one.
  4. Press Save webhook.

Each delivery is a JSON POST signed with X-Codexta-Signature: sha256=HMAC(secret, timestamp + “.” + body), the timestamp being in X-Codexta-Timestamp. The list shows the secret, when it was last called and how, and how many deliveries failed in a row.

How do I connect an agent bot?

  • Who: Owner, Admin
  • Plan: not on every plan

Codexta › Support console › Settings › Agent bots

Without the feature the tab says Your plan does not include agent bots. Upgrade the plan to use them.

  1. Press Add bot. Fill in Name and Webhook URL (where the bot hears each case’s events). Description and Avatar (https URL) are optional. Press Save bot.
  2. Copy the Access token now; it is not shown again. The bot answers with it in the header api_access_token.
  3. In Settings › Channels, open a channel and choose the bot under Agent bot. The bot takes that channel’s new cases first; a person replying takes the case over.

New token and New secret replace them (the old token stops working). Deleting a bot sends its channels back to people.

How do I add a dashboard app?

  • Who: Owner, Admin

Codexta › Support console › Settings › Dashboard apps

  1. Press Add. Fill in Title, Order and Page address (https only).
  2. Press Save.

The title appears as a tab beside Details on every case. Your page is told the case, the contact and the agent through a browser message (postMessage, event appContext).

How do I make a personal API token?

Codexta › Support console › the bell › My settings › My API tokens

Press New token, name it (what will use it?), and copy the token at once: Copy it now, it is not shown again. The list shows when each was used; Revoke ends one. Token creation and revoking are written to the audit log.

12

Data, audit and import

How do I search the audit log?

  • Who: Owner, Admin
  • Plan: any

Codexta › Support console › Settings › Data & audit › Audit log

  1. Type in Search (Who or what).
  2. What: Everything, Configuration, Data deletion, Contacts or API tokens.
  3. On: a kind of thing, such as queues, channels, members, tiers, priorities, calendars, mail settings, labels, SLA policies, saved replies, macros, automation, webhooks, API tokens or contacts.
  4. Set From and To dates, or tick Oldest first. Load more shows older rows.

Each row shows When, Who, What, On and Details; a configuration change shows what it was before and after. Events logged include a case deleted, customer data erased, configuration changed, a contact blocked or unblocked, and API tokens created or revoked.

How do I erase a customer and import an old helpdesk?

Erasing a customer is explained in erase a customer’s data.

Import. Under Import from another helpdesk, choose From Freshdesk or Intercom. For Freshdesk enter the Freshdesk domain (for example yourcompany.freshdesk.com) and the API key; for Intercom the Access token. Press Start import. Contacts, conversations, messages, private notes and tags come over; each run lists the counts (contacts, conversations, messages, skipped, errors) and a Log. A failed run has Retry. Running it again skips what is already imported.

Sign-in rule. The Sign-in box offers to require two-factor sign-in from Codexta accounts that act in your helpdesk (Codexta support staff). Your own team signs in through your shop platform, whose two-factor settings apply.