Tickets in each customer's language
Answer every customer in their own language, while your team writes in Spanish.
- Inbox, list and board
- Deadlines by priority
- Every customer in their language
-
Mailbox
Incoming email
your support mailboxes -
Ticket
CRM customer
language suggested - Paths Priority?
- Deadline Warns before a breach
- Queue By urgency
- Archive Marked as spam
-
Reply
Written in Spanish
templates · internal notes -
Customer
Reads it in their language
both texts are kept
What changes in your day-to-day.
Today
- Customer requests get lost among the team's emails.
- A customer abroad waits for someone to translate their question.
- You find out a deadline was missed when the customer complains.
With iERP
- Every customer email becomes a ticket with an owner and a priority.
- Your team writes in its own language and the customer reads in theirs.
- The queue warns you before a deadline runs out.
In their language, without changing yours.
Your team always writes in Spanish and the customer receives it in theirs. Both texts are kept, original and translation, so anyone can check what was said and what arrived.
Customer · German Der Export bricht bei mehr als 500 Zeilen ab. The export stops with more than 500 rows.
You · Spanish → German Lo hemos corregido; vuelve a probar, por favor. Wir haben es behoben, bitte versuchen Sie es erneut.
Deadlines by priority.
Each priority has its commitment in minutes and the queue is sorted by urgency, with a warning before it's breached and compliance measured on the dashboard.
- #812 · Urgent · Export error ! 3 h left
- #809 · High · Account locked ✓ On time
- #805 · Normal · Billing question ✓ Replied
- #801 · Normal · Change of details Waiting for customer
- #798 · Low · Suggestion ✓ Solved
Sample data
What Support does
Technical incidents, after-sales or admin queries: the circuit is the same and the priorities are the ones you set.
-
01
Inbox, list and board
Live tickets with instant triage — unassigned, mine, the whole team — the full history with a search box, and a board by status.
-
02
Everyday tasks, in one click
Escalate, tag, link, merge, mark as spam, schedule a follow-up and log time, without leaving the conversation.
-
03
Templates and internal notes
Reusable replies dropped straight into the composer, and notes only agents can see, on the same thread and never sent to any customer.
-
04
The customer, not the ticket
CRM accounts and contacts through a support lens: live tickets, history and average resolution time, plus the projects each issue arrives through.
Without opening iERP
51 Support actions are available to your own Claude or ChatGPT. Ask for what you would do by hand and get on with your day: it acts with your permissions; depending on its app, it asks for your permission before changing anything, and everything lands in the audit log.
- «Reply to the Nordwind ticket with the access-issue template and set a follow-up for Friday.»
- «Give me the monthly report for the board: resolved, average time and deadlines met per person.»
Your assistant · connected to iERP
Which tickets go past their deadline today, and which have been waiting a week for a reply from us?
- → 4 tickets at risk
Four tickets breach today, two of them from the same customer: I will sort them by deadline and suggest who to reassign each one to. Separately, three have been waiting a week for a reply from us. Tell me which to escalate and I will do it.
Sample data
€15 a month. Plus your users.
Every user costs the same, whatever they use. Prices exclude VAT. Requires CRM to be active. With 3 modules or more, 10% off modules. With 5 modules or more, 20% off modules.
Support does not answer alone
The customer and their contacts are the ones in CRM, the ticket hangs off the project that raised it and Automation triggers whatever repeats. Same database, same permissions, nothing to integrate.
Industries where it fits
Questions about Support
Does my team need to speak the customer's language?
No: agents always write in Spanish and the customer gets the reply in their own language. The thread keeps both texts — the original and the translation — so anyone can check what was said and what actually arrived.
How does a ticket come in, and how does the reply reach the customer?
By email: the ticket is opened from the mailbox or by hand in the inbox, and the agent's reply goes out to the customer by email, already translated. There is no separate portal your customers have to sign up for.
Can the AI answer tickets for me?
It can draft and send the reply, escalate, tag, merge, schedule a follow-up or log time, always with your permissions; depending on your assistant's app, it asks for your permission first. Replying sends a real email to the customer. Deleting or cancelling is flagged as destructive and everything lands in the audit log.
Shall we try it with your data? Half an hour, no strings attached.
We'll show you the module with your real processes and how your own assistant would use it. Or create your account and turn it on today.