报表与仪表盘
按任意字段对任意对象分组构建报表，支持计数、求和或平均，柱状图/饼图/表格图表以及 CSV 导出。还可定时发送邮件摘要，并按自己的方式搭建仪表盘。
- 对任意对象分组与聚合
- 图表、表格与 CSV 导出
- 多币种合并为基准货币
- Service analytics: ready-made reports that become your own, findings with cause and action, milestone compliance and a volume forecast that refuses to forecast without history.
在 Sellio 中免费，你只需为机器付费
BI 和高级报表通常是付费附加功能。在这里它们已包含在内：你只为机器（基础设施）付费。
针对任意对象的报表
对任意 CRM 数据进行分组、计数、求和和平均，包括你自建的对象。
一目了然的可视化
柱状图、饼图和表格把原始数字转化为管理层一眼即懂的答案。
全局数字，清晰不乱
多币种合并把跨货币的业务汇总成一个连贯的总额，助你做出可靠决策。
报表主动送到你面前
定时邮件摘要把你的指标直接送到收件箱，无需打开系统。
数据随你带走
随时导出 CSV：你的数据始终属于你，没有任何附加条件。
针对任意对象的报表，包括你自定义的对象
自动将多种货币合并为基准货币
定时邮件报表，可与团队共享
Age runs on the clock and the target runs on business hours: two readings with different names, never two numbers with the same name.
从数据到决策
选择对象、分组、指标和筛选条件。以柱状图、饼图或表格查看，并一键导出。
多币种合并
多种货币的商机会按你设定的汇率换算为基准货币，因此总额不会混用货币。
自动生成摘要
定期通过邮件发送 CRM 摘要，并共享已保存的报表。
Ready-made service reports
Whoever handles support used to open the reports screen facing a blank sheet and had to know by heart that the object is called ticket and the field is group, not team. Now there is a library of ready-made reports on the ticket: cases by status, open by priority, by channel, by category, open by team, a month-by-priority pivot, a week-by-channel pivot and a resolution cohort (of the cases opened each month, how many did I close). One click turns a preset into a report of your own, named in your language; from there it is an ordinary report, editable, shareable, exportable and schedulable like any other, with no separate engine behind it. "Open" in the presets is the same definition as the panel backlog, status outside the resolved set, so the two never disagree. CSAT, NPS, calls and incidents deliberately do not become presets: they live in tables the generic report cannot reach, and a preset that opened empty would be worse than none; their reading is the analytics tab of the console.
Service analytics · findings, milestones and forecast
The analytics tab of the console answers what no screen answered before: how long the queue has been sitting, how much of each promised milestone was met, how much escalated, what voice, bot and messaging have been doing, what incidents cost in tickets, where the volume is heading and, at the end, what to do. Every number arrives calculated by the server, so no two screens quietly disagree about the same figure. Two readings that look alike and are not: age runs on the clock, calendar time since the ticket was created, and the target runs on business hours, the SLA promise with pauses discounted. The findings (SLA below target, more coming in than going out, an aging queue, reopenings, escalation, a channel below average, a recurring root cause, a knowledge gap) come with the numbers that support them, a likely cause and an action, ordered by weight, and every detector requires a minimum base: three tickets are not a drop in satisfaction, they are three tickets. Compliance is per milestone, first response, next reply and resolution, not resolution alone: next reply is every time the customer comes back after already being answered, and only cases that had a target enter the count. Queue age comes in bands (under a day, one to three, three to seven, over a week), overall, per queue and per agent, with the oldest case in sight. Bot containment has three outcomes, not two: contained without a human, handed off to a human, and asked for a human and nobody came, which is an abandoned queue and used to hide inside the containment number. Escalation only counts what has the trace of a time rule, an unavailability or a reassignment; a manual change of owner does not count, because guessing would inflate the rate. Voice, messaging and incidents each get their own reading, because a WhatsApp conversation is not a ticket and an incident is measured by what it cost in cases and by the root cause that keeps coming back, with incidents lacking a root cause shown as explicit debt. The volume forecast is trend plus a day-of-the-week index, so Saturday is not projected as if it were Tuesday, and it requires two full weeks of history: without them it declares itself unreliable instead of drawing a confident line through noise. Where there is no base the screen shows a dash, not 0%: nobody met the target and there was nothing to meet are different statements.
- 1
选择一个对象并定义分组和指标。
- 2
选择图表：柱状图、饼图或表格。
- 3
需要时开启多币种合并。
- 4
安排邮件发送或导出为 CSV。
管理层每周一都要看数字
安排一份邮件摘要，指标就会准备就绪地送达，无需任何人工操作。
跨多个国家的业务
多币种合并把一切汇总成一个真正可比较的总额。
按来源理解漏斗
按来源对商机分组，柱状图立刻告诉你该往哪里投入。
SLA dropped and nobody knows why
The findings point out whether it was a channel below average, an aging queue or more coming in than going out, each with the numbers and an action. Whoever supervises acts on the heaviest one instead of opening five reports.
构建报表是如何运作的？
你选择对象、分组、指标（计数、求和或平均）和筛选条件，结果会以柱状图、饼图或表格呈现。
我可以针对自己创建的对象构建报表吗？
可以。报表适用于任意 CRM 对象，包括你自建的自定义对象。
有哪些图表类型可用？
柱状图、饼图和表格，并可随时导出 CSV。
我可以导出报表数据吗？
可以，随时都能导出 CSV，你的数据始终属于你。
多币种合并是如何运作的？
多种货币的商机会按你设定的汇率换算为你的基准货币，因此总额绝不会混用货币。
我可以让报表自动通过邮件发给我吗？
可以，你可以定时安排周期性的邮件摘要。
我可以与团队共享报表吗？
可以，已保存的报表可与团队共享。
我可以使用哪些聚合指标？
对所选对象的任意字段进行计数、求和和平均。
Can I try it for free?
Yes. Every new account gets 14 days of full access, no card. After that, features follow the per-user plan you choose; the full matrix is on the Plans page.
Why does the volume forecast sometimes not show up?
Because it requires at least two full weeks of history for the day-of-the-week index to have a base. With less than that, the panel declares itself unreliable instead of forecasting over noise.