How to use Tiketier if you work in the workspace: support, charge, ship and let your customer buy or book without an account.
1. What it is and who gets in
Tiketier is the place where your team serves customers. A message comes in, a ticket opens and someone —a person or a bot— answers it. In the Business plan, the same workspace also sells, tracks stock, builds orders, ships and produces.
There are two kinds of people, and they don't mix:
Your team signs in with a user account: owner, admin, agent or member. They see the menu on the left.
Your customer has no account. They come in through a link you publish: the store, an appointment, a reservation or the menu.
The menu changes based on the plan, the role and the sector. If a screen isn't there, it's almost always for one of those three reasons. Chapter 19 gathers those cases.
Tiketier charges the workspace subscription. Your customers' payments (MercadoPago, Stripe, cash, posnet) are processed by the method you connect. Argentina's electronic invoice, if you use it, goes through ARCA: it doesn't replace your accountant.
2. Sign-up and access
The app is at app.tiketier.com. Sign-up doesn't ask for a card. The plan is confirmed later, at checkout.
Create the workspace
Fill in first name, last name, organization name, country, email and a password of at least 10 characters.
Or sign in with Google or Microsoft. If that account doesn't have a workspace yet, the app asks for the organization name.
The country matters: in Argentina you'll be able to connect MercadoPago and ARCA. In other countries, card payments go through Stripe.
Signing back in
Email or username, plus password. "Remember me" remembers your username or email in that browser (it doesn't keep the session open).
You can also use Google or Microsoft, the same as at sign-up.
If Google or Microsoft aren't available, you canceled them or sign-in failed, the login screen says so. Try again or sign in with email.
If you're forced to change your password (this happens with some accounts created by an admin), you won't see the rest of the app until you change it.
Someone arriving as an invitee doesn't create another workspace: they sign in with the invitation email and the temporary password given to them by the owner or an admin.
3. Initial assistant
The first time, before the menu, there's an assistant. You see it if you're the owner or an admin and the workspace hasn't been set up yet. An invitee sees a short version.
If you set up the workspace
Welcome. It shows you the flow: a message comes in, a ticket opens, it's handled and the history stays.
Your instance. Business name, country, and your first and last name.
Industry. What the business does, and whether you sell services, products or both. That sets up the ticket categories and, in Business, opens the matching tab of the Orders hub by default (Delivery for products, Work for services).
How the company operates. Whether you manufacture to stock, to order, by project, or don't manufacture. How you charge. Whether you track lots or serial numbers. Tax details, if you want to enter them now. It can be changed later.
Tickets. Code prefix (for example TK, and cases come out TK-00012) and the categories for filtering.
Tour. It shows you the rail (CRM, ERP, Agents, Settings), the dashboard, the inbox, the bots, the chat, operations and plans.
Done. That's where the trial starts. The next useful step is usually the first ticket, WhatsApp and the support policy.
If you were invited
You see a welcome, your profile (how you'll look on tickets), a short tour and that's it. You don't set up the business.
4. How to get around
On the left there's a rail with four sectors. Each one opens its list of modules.
CRM. Customers, tickets and campaigns: dashboard, tickets, appointments, reservations, approvals, customers, pipeline, team, human resources, Instagram and Facebook, campaigns and documents.
ERP. Operations and finance. In plans that aren't Business, these screens aren't there.
Agents. Chats, Connections (WhatsApp, Instagram, Messenger and email with AI) and activity and routines.
Settings. Integrations, support policy, plans, billing and administration.
At the top:
Search modules with Ctrl+K (on Mac, ⌘K). It's the fastest way to jump to Tickets, Cash or Public store.
Branch. If there's more than one, the selector filters what you're viewing. "All branches" removes the filter.
Bell. Opens Activity and routines, where the agent asks you for a data point or an approval.
AI Copilot. From the panel you choose an agent and it takes you to the chat; it also links to the agent log and to Connections and tools.
Sign out is in the top bar.
If there's an agent task in progress, a banner at the top takes you to the detail. Below the side menu, Help center opens the app chat for short questions. This page is the long manual.
5. Plans and billing
Without an active plan (or without a valid trial) the app asks you to activate one. Go to Settings → Plans, choose and follow the checkout. Lemon Squeezy charges the subscription. You can upgrade or downgrade whenever you want; the current one is marked.
Basic plan. 1 bot and 1 seat. Tickets, WhatsApp, documents and chat. No team or operations.
Intermediate plan. 3 bots and 5 seats. Adds team, sectors and roles.
Pro plan. 7 bots and unlimited seats. Same screens as Intermediate, with more capacity.
Business plan. 15 bots and unlimited seats. Adds sales, stock, purchases, logistics, production, projects, payment and invoice integrations, CRM, campaigns, human resources, general ledger and approvals.
Prices are at Pricing and inside Plans. The workspace trial lasts about 7 days and doesn't ask for a card.
Workspace billing
In Settings → Billing you see the plan, whether you're on trial, whether the payment is overdue, the bot and seat limits, the history and cancellation. If the payment shows as overdue, a notice follows and you can keep operating: it's best to settle it before access is cut off.
If you open a module your plan doesn't include, the screen says it's not in the plan and sends you to Plans. Canceling the subscription is done from Billing. To delete the whole workspace, write to us at [email protected].
6. Team and permissions
It's in CRM → Team. Intermediate or higher is required. There you set up the people, the sectors and which branches each one sees.
Roles
Owner. There's one. They see everything, including the workspace billing. You can't invite another owner from this screen.
Admin. Configures tickets and bots, invites people and operates. They can also manage billing.
Agent. Handles tickets and conversations. Charges and uses Cash if the plan and sector allow it. Doesn't change the structure (categories, users, bots).
Member. Read-only. Limited access: sees what the sector allows, generally without modifying.
Invite
Choose role (admin, agent or member), sectors and branches.
The person receives a temporary password. On first sign-in they may have to change it.
Each person takes a seat. If you've reached the limit, the screen offers to expand the plan. The owner counts.
Sectors
A sector (Sales, Warehouse, Administration) defines which pages those people see, whether they see the dashboard and whether they see amounts. Owner and admin see everything the same.
As long as there are no sectors, everyone sees everything.
Anyone left without a sector only sees tickets, until you assign one.
Deleting a sector doesn't delete the people.
7. The support day
Dashboard
It's the first screen of the CRM. It shows open tickets, on-hold tickets, high priority, messages from the last 7 days, pending approvals and the CRM pipeline, plus a health panel with bots. From there you jump to the inbox, the bots or an integration you haven't connected yet.
Ticket inbox
In Tickets you search by text and filter by status, priority, "needs a human" and SLA-breached. The briefing at the top summarizes the day.
Create a ticket (if your role can manage them): you enter the case data. The extra fields, categories, priorities and statuses are defined in Administration → Tickets. Each case comes out with a code, for example TK-00018.
Inside the ticket
Change status, priority, category and who it's assigned to.
A internal note is seen by the team. A customer reply is what goes out.
If the case came from a WhatsApp bot and there's a phone number, you can reply via WhatsApp from the record.
The history stays on the same ticket. If the link is old or the case doesn't exist, you see a notice and go back to the inbox.
When a bot escalates, the ticket is marked, moves to "on hold" and is assigned to the person or sector in the policy. The "Needs a human" filter is the queue for those cases. The bot stops answering on its own until a person replies or the ticket is closed.
8. Support policy
It's in Settings → Support policy. It's mandatory: without confirming it you can't activate a WhatsApp bot or let an agent answer on its own on Instagram or Facebook.
There you decide what the AI can resolve and when it has to hand the case to a person:
Quotes, refunds and exceptions. For each one, whether the bot resolves it or always escalates. For quotes you can set a cap ("up to this amount").
Order status. Whether it can look at orders and stock to answer, or always escalates.
Scope. Whether it only talks about your business, or about anything.
No source, escalate. It's on by default. If it can't find the data in your documents or in operations, it doesn't make up the price: it escalates.
Trigger phrases. For example "talk to a person" or "cancel". As soon as the customer writes them, it escalates, without going through the AI.
Maximum attempts. How many unresolved messages trigger the hand-off to a person.
Who it's assigned to the escalated case: a person or a sector. If you don't choose, it goes to the owner.
Hand-off message that the customer reads. The email notice only goes out if the server has email configured; if not, the notice stays in the app.
In the same policy is the write autonomy of internal agents. By default they don't create sales, change tickets or release logistics on their own: those actions require approval. If you enable it, the agent can do them without asking. It's best to leave it off until the team is comfortable.
When you're done, tap Save and confirm policy. Only then is activating channels unlocked.
9. Connections: WhatsApp, Instagram, Messenger and email
Every support channel lives in Agents → Connections. Each connection has its own AI agent and tone, and you choose whether the AI or the team replies. The customer's message opens a ticket and lands in a unified inbox. Depending on the policy, the AI replies or escalates to a person.
Before connecting
An agent has to exist. If the list is empty, create one in Administration → Agents.
Confirm the support policy: without it the AI doesn't reply on its own.
Check the WhatsApp number quota: 1, 3, 7 or 15 depending on the plan.
Each channel
WhatsApp. With a QR code: on your phone, WhatsApp → Linked devices → Link, and scan the code. With Meta's official API: sign-up goes through Facebook and you connect the number from your WhatsApp Business account.
Instagram and Messenger. A single Meta sign-in: you pick which Facebook pages and linked Instagram accounts Tiketier handles.
Email. Pick Gmail, Outlook, Zoho or another server and add the mailbox with an app password. Mail is read every minute and replies go out from the same address, in the same thread, with the ticket code in the subject.
AI per connection
Replying agent. It uses its tools and the knowledge base.
Reply tone. Personality, style, language and greeting, built in the Tones tab and reused across channels.
AI or team replies. One click, also from each connection's switch.
In the Inbox you filter by channel or connection, reply through the right channel and can take over a conversation so the AI stops answering until you hand it back. When the customer asks for a person, or a policy rule is met, the case shows "needs a person".
10. Comments and posts
It's in CRM → Instagram and Facebook. Accounts and direct messages are managed in Connections; the marketing work stays here:
Comments. Those on your posts: reply or hide.
Posts. Draft, scheduled, published or failed.
11. Documents and chat
Documents
In CRM → Documents you upload what the agent has to know: price lists, policies, manuals. It accepts PDF, Word, text, Markdown, CSV and Excel. Each file goes through processing: if it fails, it's marked and you can upload it again.
Import from your website it searches pages on the same domain, you choose which ones to add, and they become available just like a file. Organize them into collections. You can view them as a list or a grid.
Chat with an agent
In the sector Agents, open a new chat or an old one.
Choose the agent and the model the workspace has enabled.
Choose the context: your sector (Own), all allowed sectors (Global) or mixed.
Web search is turned on separately, if you want it in that conversation.
The answer arrives as it's written. You can edit one of your messages, regenerate a response and delete the conversation.
When the agent relies on a file, it shows the source. If there's no source and the policy requires it, on customer-facing channels it escalates instead of making things up.
The Copilot in the top bar opens the chat from a panel: you choose an agent and it takes you to the conversation. Chat permission is required: a very restricted member may not see it.
12. Agent tasks
Agents → Activity and routines is the work the agent does in the background, not the chat with a customer.
Activity. Tasks you launched or that were triggered on their own. Statuses: queued, in progress, waiting for data, waiting for approval, finished, failed or canceled.
Routines. The same, scheduled: every day, business days, at a certain interval or at specific hours.
Open the detail to see the steps and the result. If the agent stops, it asks you there. If the action is sensitive (and write autonomy is off, or that tool requires approval), you see Approve, Request changes (with a note) or Cancel.
The bell and the top banner take you to those pending tasks. Don't confuse them with Approvals in the CRM: those are people's leave requests, purchases and expenses, not AI actions.
Which tools each agent can use, and whether each one is automatic, requires approval or is prohibited, is defined in that agent's permission (chapter 18).
13. Appointments, reservations and menu
They're three different public links. Your customer doesn't register. You set them up in the CRM.
Appointments
In Appointments you set up services, hours, appointment duration, lead time and whether the calendar is enabled. Copy the public link and share it.
Your customer chooses a service, a branch if there's more than one, day, time, name and phone, and confirms. Then they see the confirmation screen. If the calendar is off or the link is wrong, they see that it can't be booked.
In your calendar you see the appointments and change the status. The link looks like /turnos/tu-negocio.
Reservations and menu
In Reservations there are four tabs: Calendar, Tables, Menu and Settings.
The menu is built by categories. The public link is /menu/tu-negocio. If there are no items, the customer sees an empty menu. From the menu they can go to booking, if reservations are active.
The reservations link is /reservas/tu-negocio. The customer chooses party size, branch, date, time slot, their details and a note.
In your calendar the status goes through pending, confirmed, seated, completed, canceled or no-show.
14. Store
The public store is for the Business plan. Your customer buys without an account.
Getting it ready
In Products, check Show in store on what you want to publish. Price, variants and photo come from that record.
In Settings → Public store you define the short link name (the slug), the brand, the banner and the color. The address becomes /tienda/tu-negocio.
If neither MercadoPago nor Stripe is connected, the screen warns you. Without a payment method, the checkout can close via WhatsApp instead of a hosted payment.
What your customer does
They see the catalog, choose variants, build the cart and leave their name and phone. If there are branches, they choose one.
They pay on the MercadoPago or Stripe page. Tiketier doesn't see or store the card number.
Then they go to the order status: waiting, paid or canceled. When the payment is confirmed, they can go back to the store.
That sale shows up in Sales notes. The rest of the flow (assembly, delivery, delivery note) is in the operations chapter.
15. Operations
All of this is Business plan, sector ERP. If you sell services, the assistant puts work orders and projects up front. If you sell products, it puts deliveries, assembly and production up front. If you sell both, the Orders hub gathers all four types.
Overview
Operations overview shows the period and the branch, and shortcuts to checkout, sales, stock and orders.
Checkout and Cash
In Checkout you search or scan a product, build the cart, choose a customer and a mode.
Express · deliver now. It deducts stock and doesn't generate a delivery order.
Scheduled. You request a date (deadline or flexible). If there are goods, the delivery order is then created. If there are services, the job is created alongside the project.
To charge: cash, transfer, posnet (with coupon number), MercadoPago or Stripe if the country has them, or save as draft. If there's no open Cash session, you can still charge, but cash and posnet don't go into the closing: the checkout warns you and sends you to Cash.
In Cash you open the session, record movements and close it. The Cash number (CA-0001, CA-0002…) is the session's, not the branch's.
Sales notes, customers and products
Sales notes. List, filters and record: payments, status, deliveries and linked projects. To void it, open the note and void it: the stock comes back and the cash payments from the still-open Cash session are reversed. If you only want to undo one payment, void that payment, not the whole sale.
Customers. The commercial record, also visible from the CRM. Contact and tax details.
Products. Goods, services or materials. Variants, SKU, barcode, price and "Show in store". If the product is manufactured, in Manufacturing you define its recipe (which other products it's made from).
Stock, purchases and supplier invoices
Stock. Stock levels, movements and lots. Adjusting inventory is done by whoever has that permission, not just any user who can view the screen.
Suppliers and Purchases and expenses. Every registered expense creates a request in Approvals.
Supplier invoices. You upload a PDF or a photo. Tiketier reads the issuer, CUIT, dates, amounts and IVA. Review before exporting. The workspace destination can be a CSV with the columns you define, an HTTP send to a connection you've already set up, or both.
Import spreadsheets
From Customers, Sales, Stock or Logistics there's Import with AI. You upload Excel or CSV, the reading proposes which field each column goes to, what it doesn't recognize becomes extra data (read-only), you see the preview and confirm. The history of batches and rows, with their status, is in Imports.
Orders, assembly and delivery
The hub Orders gathers delivery, assembly, production and work. You can also enter each one through its module.
Delivery orders. They're created when you confirm a scheduled note with goods. They go from "to prepare" to delivered or canceled.
Assembly. The warehouse marks the quantity of each line, or the shortage. Only then is it released to logistics.
Production. It's for manufacturable products: in Products → Edit product → Manufacturing you turn on "Manufactured" and load its recipe (which other products it's made from, with quantity and scrap). The order is created automatically when you confirm a scheduled sale, or by hand by choosing the product. When you release it, materials are reserved; when you complete it, they're consumed and the finished product is added to stock. Shop floor is the floor view.
Work orders and Projects. They're created with a scheduled sale that has services. The project groups the work; the work order is the task.
Logistics, Andreani and delivery notes
In Logistics you set up zones, vehicles, carriers, jobs and trips. Open a trip to see the detail and move the status.
Andreani is optional and lives on that same screen. You enter the contract username and password, plus the origin (name, CUIT, address) if the shipment requires it. Andreani shipments are listed there. It doesn't replace your internal trips: it's shipping through that company.
The delivery note is issued automatically when a shipment (trip or job) moves to dispatched. It's linked to the delivery order and the sales note. In Delivery notes you open it and print it with the browser. In the normal flow you don't need to create it by hand.
Quotes, cost and ledger
Quotes and certifications. Commercial documents (quote, invoice, certification, change) with costs, waste, contingency and margin. Invoices and certifications post to the general ledger.
Job cost. The recipe's standard cost against the actual cost (materials, labor and machine) of a production order.
General ledger. Movements to track the workspace's money. It's not an accounting system and doesn't close IVA: your accountant still does that. ARCA, in Connections, issues the electronic invoice.
Branches
In Branches you create each location. Then, in Team, you decide who sees each one. The top selector filters the day's operations.
16. Relationships and people
It's also Business plan, except Team, which is already there from Intermediate (chapter 6).
CRM pipeline. Opportunities board. You create one with a title and amount and move it between stages. It doesn't replace the Customers record: the pipeline is the sales follow-up, the customer is the account.
Campaigns. Calendar with draft, active, paused and finished statuses. From there you jump to Instagram and Facebook to publish.
Human resources. Employees, departments and leave requests. A leave request can generate a request in Approvals.
Approvals. Leave, purchase and expense requests. If it's pending, you approve or reject it. If there's nothing, the screen stays empty: that's normal.
17. Connections
Almost all of them live in Settings. Cash and transfer are always there; the rest is connected if you use it.
Payments and invoicing
In ERP integrations (Business plan):
MercadoPago, if the workspace is from Argentina. The customer pays at the MercadoPago checkout, in the store or from the POS.
Stripe, if the workspace isn't from Argentina. Same role.
ARCA, in Argentina: CUIT, point of sale and certificates. It issues the electronic invoice (A, B or C as applicable). It doesn't do the accounting.
Disconnecting is from the same screen. Tiketier doesn't store card numbers.
TiendaNube
You connect the store with the TiendaNube login, sync orders and import them as draft sales notes to review before confirming.
Google
Google Drive and Calendar is separate from "sign in with Google". Here you authorize the workspace to view and upload files, and to view and create events. You can disconnect whenever you want.
MCP, for an external assistant
If you want Claude, Cursor or ChatGPT to read data from this workspace (customers, sales, orders, stock):
Go to Settings → MCP.
Generate a token. Copy the address and the token into that tool's configuration file, as the screen shows you.
Don't share it outside the team. If it leaked, revoke it and generate another. The old one stops working immediately.
The HTTP connections and the ERP tools (so an agent can call another system) are in Administration, not on this screen.
18. Administration
The owner and anyone with administration access sees it. A support agent can't get in. It's in the Settings sector.
Tickets. Statuses, priorities, categories, custom fields, code prefix and whether you can reply via WhatsApp.
Agents. Create the virtual employees and assign them models. The sector is assigned to people in Users. Without this there are no bots or chat.
Agent permissions. From the agent, which tools it can use and whether each one is automatic, requires approval or is prohibited.
Presets. Templates so you don't configure each bot from scratch.
Knowledge base and collections. The file that feeds the answers, in addition to what each person uploads in Documents.
Models. Which AI models the workspace can choose in the chat.
HTTP connections. An external API for a tool of the agent to call.
Tools. Turn on, turn off or set to trial the operations tools.
Jobs. The processing queue (a document, an invoice read). You can retry or cancel.
Users. The workspace accounts, in addition to the Team screen.
Sync Ubiar. If your operation is in that system, it syncs from there. If you don't use it, no need to touch it.
19. When something doesn't show up
I can't see a module. Check the plan (Business to sell and operate; Intermediate for team), the role and the sector. Owner and admin see everything. Without sectors, everyone sees everything. Without an assigned sector, that person only sees tickets.
The screen says the module isn't in the plan. Go to Plans and upgrade, or ask the owner to do it.
It asks me to activate a plan and won't let me in. The trial ended or there's no subscription. Plans → checkout. If the payment is overdue, you can generally keep going, with the notice in Billing.
I can't activate the bot or the network. Confirm the support policy. Then check that an agent exists, that you haven't reached the bot limit and that the platform is accepting new sign-ups.
The bot makes things up or doesn't escalate. In the policy, leave "no source, escalate" on, enter the trigger phrases and upload the prices to Documents.
Cash doesn't appear in the Cash closing. The checkout was used without an open Cash session. Open Cash before charging in cash or posnet.
The store, the appointment or the reservation "don't exist". The link doesn't match the slug, or the calendar or the store is disabled. Check Public store, Appointments or Reservations and copy the link again.
The store doesn't charge by card. MercadoPago (Argentina) or Stripe (other countries) is missing in ERP integrations. Without that, checkout can go via WhatsApp.
I can't invite anyone else. You've reached the seat limit. In Team it offers to expand the plan.
I can't see amounts. The sector has amounts hidden. An admin changes it in Team → sector.
One page failed and the rest keeps working. Go back to the menu and try again. If it happens again, write to us with the name of the screen.
For a specific question, inside the app, the Help center in the menu answers with what's loaded in your workspace. For the full tour, this guide.