Skip to content
Reportkey
Usedesk
Omnichannel Usedesk

Usedesk customer inquiry report by channel and agent

Reportkey exports Usedesk tickets and shows which channels customers use to reach support, how many inquiries stay open and how the flow spreads across agents and groups, in one report with your ads and sales.

Sign up, add the API channel token from Usedesk and pick the account in a project. Your first report in 5 minutes.
  • New tickets for each Usedesk channel with its share.
  • Open, completed, closed, pending and spam tickets.
  • Workload by agent, group, priority and type.
Sample Reportkey client report
Sample Reportkey client report
Usedesk Tickets by channel, status, agent, and tag
30+
integrations
5 min
setup
14 days
trial
TL;DR

Usedesk integration: enter the token of an API-type channel from Usedesk settings once on the integrations page and pick the account in a project. New, open and closed tickets by channel, status, agent, group and tag reach the client as a link or PDF on schedule.

Customer inquiry reports for marketing and management

Usedesk pulls email, messenger and social messages and website chat into one inbox. Agents love that, but marketing and management usually notice support only through complaints. Yet inquiry flow follows advertising directly: a sale, a new campaign or a delivery failure shows up in ticket volume right away. Reportkey reads tickets from Usedesk through the API and turns them into a section of a recurring report that sits beside ads, the website and sales.

Connecting Usedesk through an API channel

Usedesk grants data access through a dedicated API-type channel. Add it in Usedesk settings and the channel receives a token. Enter that token once on the Reportkey integrations page. Companies on a server or regional Usedesk installation also need its API address, which Usedesk support provides. In the project, pick the account, report blocks and a schedule.

Support tickets by channel

The main block shows how many new tickets arrived per day, week or month and how they split across Usedesk channels, each with its count and share of the total. It answers the marketer’s question of where customers go with questions after an ad: email, a messenger or website chat. If one channel’s share jumps, check whether ads or landing pages point there.

Ticket statuses: open versus resolved

The second block groups tickets by Usedesk status:

  • open — need work;
  • completed — answered and awaiting confirmation;
  • closed — finished;
  • pending — on hold until the customer or a third party responds;
  • spam — filtered out.

The period-end snapshot shows the backlog carried into next week, and the status trend shows whether the team keeps pace with demand.

Support agent workload

The workload block counts tickets per agent and per group, split by priority and type. A contact centre manager sees who is overloaded and which groups receive more urgent requests. An agency sees that a post-campaign spike landed on a specific group, for example the delivery desk.

Inquiry topics by tag

Tags that agents and Usedesk rules apply to tickets add up to a topic view by channel. For marketers it hints at ad and landing page copy: if questions about applying a promo code grow, the offer terms were explained poorly.

Why the report has no response time

The Usedesk ticket list includes SLA fields, but they hold current deadlines for answering or closing a ticket, not measured response time. Reportkey does not present a deadline as a fact, so the report describes flow, statuses and work distribution. Two more details: status and assignee are current at export time, and Usedesk dates arrive in UTC and are converted to the report time zone.

Usedesk next to ads, calls and CRM

To link inquiry flow with its causes, add Calltouch or CoMagic calls, Roistat end-to-end analytics and orders or deals from RetailCRM, amoCRM or Bitrix24. Branding and AI insights are available, though not on every plan. See a multi-channel example in the PPC agency demo report, more inquiry tools under support and live chat, and terms on pricing.

Metrics

What goes into the Usedesk report

These are the metrics that the Usedesk integration already brings into Reportkey reports.

New tickets
Closed tickets
Open tickets
By channel
By agent
What this integration adds to the report
Tickets by channel, status, agent, and tag
Pricing

Usedesk reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect Usedesk to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from Usedesk in client reports.

Pain points
  • Tickets reach Usedesk from email, messengers, social networks and chat, yet the marketer cannot see which channel grew after an ad launch.
  • Once a month a senior agent filters tickets by status and assignee and copies the numbers into a management deck.
  • Ticket tags pile up for years, and nobody watches which topics grow until complaints reach the director.
Usedesk
An online store with omnichannel support

Each week the marketer sees how many new tickets arrived in every Usedesk channel and how many remain open. When a sale lifts messenger traffic, the team has time to rebalance shifts.

Usedesk
An agency running ads and caring about customer experience

Next to ad spend and leads, the report carries a support section with tickets by channel and status for the same dates. The client sees that more advertising also changed the workload, not just sales.

Usedesk
A contact centre manager

A report by agent and group, split by priority and ticket type, goes to the director on schedule. Discussions focus on how work is shared rather than on export accuracy.

Report preview

How Usedesk appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

  • Inquiry topics by tag, split by channel.
Sample Reportkey client report
Sample Reportkey client report
Monthly support section

Stacked weekly bars of new tickets by channel, a status ring at month end, an agent table with ticket counts and a cloud of the most frequent tags.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the Usedesk connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the Usedesk account and channels or groups that should supply conversations, tickets, and response times to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

What do I need to connect Usedesk?
The token of an API-type channel, created by adding an API channel in Usedesk settings. If you use a server or regional Usedesk installation, you also need its API address. Both values are entered once on the integrations page.
Will the report show first response time?
No. The Usedesk ticket list returns current SLA deadlines, meaning when a ticket must be answered or closed, not the measured response time. Presenting a deadline as a measurement would mislead, so the report covers flow, statuses and workload.
Why is a ticket counted under a different agent?
Status and assignee reflect the moment of export. If a ticket was reassigned, it counts under the new assignee even if the previous one did most of the work. Keep that in mind for last month's workload.
Which time zone do dates use?
Usedesk returns dates in UTC. Reportkey converts them to the report time zone, so tickets created late in the evening land on the correct day rather than the previous one.
Are there volume or frequency limits?
Usedesk returns one hundred tickets per page, so a large archive loads page by page. Requests with free-text search are limited to ten per minute; reports do not need them, since selection uses dates, channels and statuses.

Usedesk customer inquiry report by channel and agent

Sign up, add the API channel token from Usedesk and pick the account in a project. Your first report in 5 minutes.

Start free