Support Ticket System
Every request becomes a tracked ticket with an ID, owner, priority and full audit trail — from first contact to resolution.
Loading Yumilo
Yumilo helps businesses manage customer conversations, support tickets, knowledge bases, service requests, and customer communications from one secure platform.
Support teams at product companies run on Yumilo
Fourteen connected modules replace the spreadsheets, shared mailboxes and side chats that slow support teams down. Every conversation, customer and service request stays in a single searchable history.
Every request becomes a tracked ticket with an ID, owner, priority and full audit trail — from first contact to resolution.
Email, chat, web forms and portal requests arrive in one queue. Collision detection shows who is already typing a reply.
A branded self-service space where customers submit requests, track ticket status and reopen past conversations.
Publish help articles with categories, versioning and review dates. Agents insert them into replies in two clicks.
Route, tag, escalate and close tickets with if-this-then-that rules. No scripting required, full change history kept.
Define first-response and resolution targets per plan, priority or customer, with breach warnings before deadlines pass.
Track volume, response times, backlog, resolution rate and CSAT by team, channel, agent or time period.
Drop a lightweight widget on your site or app. Chats become tickets automatically when a conversation goes unanswered.
Transactional updates for created, assigned, updated and closed tickets — sent only to people involved in the request.
One chronological view of every ticket, reply, plan change and login for a customer, so nobody asks the same question twice.
Granular roles for agents, team leads, admins and read-only observers, with per-team visibility of queues and reports.
Screenshots, logs and documents up to 50 MB per file, virus-scanned on upload and served over expiring signed links.
Private notes and @mentions that stay inside your team — never included in customer-facing replies or email threads.
Reusable answers with merge fields for name, plan and ticket ID, so common questions get consistent, accurate responses.
Yumilo ships with queue structures, SLA presets and article templates tuned to eight common support models. Start from a template, then adapt it to your workflow.
Handle product questions and complaints across email, chat and portal with one queue and one customer history.
Track incidents, hardware requests and access changes with approval steps and an asset field on every ticket.
HR, finance and facilities requests from employees, kept private per department with confidential ticket types.
Order lookups, returns and delivery issues, with order ID and shipment status shown beside the conversation.
Tie tickets to plans, seats and billing state so agents know account value and entitlements before replying.
Student, parent and faculty requests routed by campus and term, with quiet hours during exam periods.
Appointment, billing and administrative requests with strict access controls and complete audit logging.
Client requests grouped by engagement, with time tracking on tickets and monthly service reports per client.
Queue health, response times and satisfaction on one screen. Switch sections in the sidebar to see how the workspace is organised.
Monday, 09:14 UTC · Support team overview
Adi Rahman replied to ticket #45892
2 minutes ago · BillingSiti Damayanti resolved #45871 after 3 replies
18 minutes ago · TechnicalAutomation rule Escalate aging tickets moved 4 tickets to Tier 2
41 minutes ago · AutomationMaya Pratiwi published article Resetting your password
1 hour ago · Knowledge BaseDimas Kurnia assigned #45903 to the Payments queue
2 hours ago · RoutingConversation history, internal notes, attachments and customer details sit side by side, so an agent picking up a ticket never has to guess what happened before.
Invoice charged twice for the September billing cycle · Channel: Email · Created 09:02 UTC
Hi, our card was charged twice for the September invoice — INV-2026-0918 and INV-2026-0919 have the same amount and the same date. Could you check and refund the duplicate? I've attached both receipts.
Hi Sarah, thanks for the details and the receipts — that made this quick to verify. I can confirm INV-2026-0919 is a duplicate created by a retry on our payment gateway. I've submitted the refund, and it will appear on your statement within 3–5 business days. I'm keeping this ticket open until you confirm you've received it.
@dimas the gateway retried the charge after a 504 at 03:11 UTC. Six accounts are affected in the same window — I've opened #45905 for engineering so we can add idempotency keys on retries. No customer action needed for the others; refunds are queued.
That was fast, thank you. One more thing — can you make sure the finance contact on our account receives the refund receipt as well? Her address is finance@northbayretail.example.
Yumilo raises an in-app notification for every meaningful event on a ticket or account. Each one links straight to the record it describes, and every agent controls which events also reach their inbox.
#45914 — “Cannot upload attachment over 20 MB” from Vantablue.
Adi Rahman replied to #45892 — refund confirmed for INV-2026-0919.
#45903 was assigned to you by Dimas Kurnia — Payments queue.
#45888 raised from Normal to Urgent — SLA target now 1 hour.
#45871 was resolved by Siti Damayanti. A satisfaction survey was sent.
Your account password was updated. If this wasn't you, contact security immediately.
Sign-in from Chrome on macOS · Jakarta, Indonesia · IP 103.***.**.42
Invoice INV-2026-1042 for the Business plan is ready — $149.00, due 15 August.
Sarah Lestari rated ticket #45871 five stars: “Answered in minutes, problem gone.”
A transactional email is a message sent because a specific person did a specific thing — signing up, resetting a password, opening a ticket or receiving a reply. Yumilo generates these messages in response to authenticated actions and support workflows, delivers them over authenticated domains, and records the delivery result on the related ticket or account.
Yumilo only sends transactional emails triggered by authenticated user actions or customer support workflows. The platform does not send unsolicited marketing or promotional email campaigns.
Hi Sarah,
Adi Rahman from the Billing team replied to your request about the duplicate charge on invoice INV-2026-0919. A refund of $149.00 has been submitted and should reach your statement within 3–5 business days.
View ticket #45892
You can also reply directly to this email — your response is added to the ticket automatically.
Every message is signed with DKIM and aligned under SPF and DMARC before it leaves our infrastructure.
Sent, delivered, bounced and complaint events are written to the ticket record and the account audit log.
Support inboxes hold order details, account data and private complaints. Yumilo treats that content as sensitive by default — in transit, at rest and in the audit record.
TLS 1.3 for all traffic, AES-256 encryption at rest, and HSTS enforced on every subdomain.
Sender Policy Framework records authorise only our verified sending infrastructure.
Every outbound message is cryptographically signed so recipients can verify it is genuinely from us.
A published DMARC policy with aggregate reporting blocks spoofing of the yumilo.web.id domain.
Passwords are stored as salted Argon2id hashes. Plain-text credentials are never written to disk or logs.
Optional OAuth 2.0 sign-in so teams can keep identity, offboarding and MFA policy in Google Workspace.
Short-lived signed sessions, rotation on privilege change, and instant revocation from any device.
Who viewed, edited, exported or deleted a record — retained and exportable for compliance reviews.
New device or unusual location sign-ins trigger an immediate email to the account owner.
See every active session with browser, platform, location and last activity — and end any of them.
Around a third of incoming requests are questions already answered somewhere. A well-maintained knowledge base turns those into instant self-service — and gives agents a canonical answer to send.
Set up your workspace, invite agents and receive your first ticket in under an hour.
Profiles, passwords, workspace membership and single sign-on configuration.
Plans, seats, invoices, payment methods and how proration is calculated.
Day-to-day agent workflow: queues, macros, SLA timers and satisfaction surveys.
Access control, audit logs, device management and incident reporting.
REST endpoints, webhooks, rate limits and authentication for building on Yumilo.
Connect Yumilo to the tools your team already uses without custom development.
Practical writing from the people who build Yumilo and the teams who use it every day — no growth-hacking, just how support work actually gets better.
Four structural changes — queue design, macros, escalation paths and a maintained knowledge base — that cut workload before headcount becomes the answer.
Why median first-response time beats average, how to find the queue that quietly eats your SLA, and what routing rules to write first.
Lead with the answer, name the next step, and drop the phrases that make customers feel processed rather than helped — with before-and-after examples.
Nine habits that survive a busy Monday: ownership rules, escalation etiquette, tone standards and the weekly review that keeps them alive.
Verification before disclosure, redaction habits, safe attachment handling and what to do in the first ten minutes of a suspected account compromise.
Support operations, metrics, tooling and team leadership — published every other week.
Every plan includes the ticket system, shared inbox, customer portal and knowledge base. You only move up a tier when you need deeper automation, reporting or governance.
For small teams answering their first support emails in one place.
Free for up to 3 agents, forever
For growing support teams that need automation and real reporting.
Billed monthly · Minimum 3 agents
For multi-team operations with custom workflows and integrations.
Billed monthly · Minimum 5 agents
For regulated organisations with procurement and compliance requirements.
Annual agreement · Volume pricing
All prices in USD, excluding local taxes. Cancel or change plan at any time — changes are prorated to the day. Questions about procurement? Email sales@yumilo.web.id
Teams of three and teams of ninety use the same platform. These are the outcomes they report after switching from shared mailboxes or legacy help desks.
“We ran support out of a shared mailbox for four years and told ourselves it was fine. Two weeks after moving to Yumilo our first-response time dropped from six hours to under twenty minutes, mostly because nothing sits unassigned anymore.”
“The internal notes feature quietly solved our biggest problem. Engineering context stays on the ticket instead of scattered across chat threads, so whoever picks it up next already knows what was tried.”
“Our compliance team approved Yumilo faster than any tool we've bought. Audit logs, device history and configurable retention answered most of the questionnaire before we filled it in.”
“During our December peak we handled 3.4× normal volume with the same eleven agents. The overflow routing rules and saved replies did the work we would otherwise have hired temps for.”
“Publishing thirty knowledge base articles cut our ticket volume by a fifth in one term. Students find the answer at 2 a.m. instead of emailing the registrar and waiting until Monday.”
“I finally have numbers I trust in the monthly review. Backlog, median response, resolution rate and CSAT per agent — all from the same source, no spreadsheet assembly on a Friday night.”
Yumilo started in 2021 with four people who had spent years answering tickets for other companies. We were tired of help desks that billed per feature and still made customers repeat themselves. So we built one that doesn't.
To give every support team — three agents or three hundred — a single, secure place to hold customer conversations, so that no request is lost, repeated or answered twice.
A world where contacting support is unremarkable — you ask once, in whatever channel you have open, and get a clear, accountable answer from someone who already has the context.
Four commitments we hold ourselves to, and that customers are welcome to hold us to as well.
Plain language in the product, the docs and our own support replies.
Encryption, audit logs and retention controls ship on every plan, including free.
Reliability and bug fixes come before new surface area.
Every engineer takes support shifts. It shapes what we build next.
Yumilo is a single multi-tenant application with four connected layers. Requests arrive through any channel, land in one queue, are enriched with customer history, and leave an audit record that reporting and compliance can both rely on.
Email, live chat, customer portal, web forms and the REST API all create the same ticket object — no channel is a second-class citizen.
Automation rules assign owner, team, priority and SLA target within seconds, using customer plan, keywords and business hours.
Agents work in the shared inbox with full customer timeline, internal notes, saved replies and knowledge base articles at hand.
Every resolution feeds analytics, CSAT and article gap reports, so next month's queue is smaller than this month's.
Ticket activity, agent responses, customer replies, status changes and login history in one chronological stream — filterable per customer, per agent or per ticket.
Sarah Lestari submitted “Invoice charged twice for the September billing cycle” via email with two attachments.
Rule billing-keywords set category Billing, priority High and a 4-hour resolution target.
Routed to Adi Rahman (Billing team, Tier 2) — lowest open load in the queue.
First reply delivered in 5m 12s, within the 30-minute first-response SLA. Refund confirmed.
Adi Rahman mentioned @dimas about the gateway retry and linked engineering ticket #45905.
Sarah asked to copy the finance contact on the refund receipt. SLA timer paused pending agent action.
Status remains Open · Awaiting agent. Watchers notified: Dimas K., Rani N.
Chrome 141 on macOS · Jakarta, Indonesia · IP 103.***.**.42 · Trusted device
Signed out manually from the agent workspace. Session token revoked immediately.
Promoted from Agent to Tier 2 Agent by Rani Nurhaliza. Now able to issue refunds up to $500.
First sign-in from Safari on iPadOS. A security email was sent and the device was confirmed.
Password updated from account settings. All other sessions were signed out automatically.
Downloaded “Billing queue — July response times” as CSV. Export recorded in the audit log.
Whether you're evaluating Yumilo, need help with your workspace, or want to report a vulnerability, there's a direct address for it below.
Monday–Friday · 09:00–18:00 UTC
Enterprise customers with a 24/7 support agreement can reach the on-call team at any hour through the portal.Yumilo · Jakarta, Indonesia · Remote-first team across 6 time zones. Map shown is an illustrative placeholder — request exact directions from sales before visiting.
The seven questions our own support team answers most often. If yours isn't here, email support@yumilo.web.id and we'll add it.
Customers can create a ticket in four ways: emailing your connected support address, submitting the form in the customer portal, starting a live chat that goes unanswered, or through the REST API. Agents can also create a ticket manually from the workspace — useful when a request arrives by phone. Whichever route is used, the ticket gets an ID, an owner, a priority and a full activity record from the first second.
Select “Forgot password” on the login screen and enter your account email. We send a single-use reset link that expires after 30 minutes. Opening the link lets you set a new password, and every other active session is signed out automatically. You'll also receive a confirmation email — if you get one you didn't request, contact security@yumilo.web.id straight away.
Every notification email includes a secure link to the ticket in the customer portal, showing current status, assigned team, the full conversation and any attachments. Customers who create an account can see all their past and present tickets in one list, filter by status, and reopen a resolved ticket within 14 days instead of starting over.
The portal is your branded self-service space: submit a new request with the right form fields, track open tickets, read knowledge base articles, download invoices and manage which notifications they receive. You control the logo, colours, domain and which categories are publicly visible. Portals can be open to anyone or restricted to verified customers only.
You're billed per active agent seat. Adding a seat mid-cycle is prorated to the day; removing one credits the unused portion to your next invoice. Deactivated agents keep their ticket history but stop counting toward billing immediately. Switching from monthly to annual applies the 20% discount from the next cycle, and there is no charge for customer portal users — only agents.
Every invoice is emailed to your billing contact when it's generated and stored under Settings → Billing → Invoices, where you can download a PDF of any past invoice. You can add a second billing email, set your company name, tax ID and billing address, and those details appear on all future documents. Payment receipts are sent separately once a charge succeeds.
Every plan — including the free Starter tier — gets email support at support@yumilo.web.id, the full knowledge base and the status page. Professional and Business plans add live chat during business hours and guided migration from your current help desk. Enterprise agreements include 24/7 on-call response, a named onboarding manager and quarterly service reviews.
Still stuck? Our team answers in under two hours on business days.