Keep players informed and engaged.
Connect every reply with player support.
Extend your existing Zendesk operation with CXBOX HUB for targeted game updates, messaging campaigns and configured follow-ups across supported channels.
Reach selected player audiences with relevant information. When they reply, continue through your configured Zendesk player-support process.
For game publishers, studios and live-service game operators. Built for player support, community operations and player communications teams. Developed by DEMETER ICT.
Meet players on the channels
they use in each market.
Connect player engagement and conversations across WhatsApp, LINE, Facebook Messenger, Telegram, Viber, X, Instagram and WeChat OA, plus messaging within your mobile app through the configured in-app messaging setup.
Choose channels around your player audience and service process. The same announcement can have different content and sending requirements in each channel.
Social and messaging channels.
Plan targeted outreach and reply handling for your selected markets and supported channel connections.
Messaging in your mobile app.
Include in-app conversations in the service journey. Confirm the required SDK or integration and how messages reach Zendesk.
Configure each workflow.
Confirm audience eligibility, message formats, sending permissions, link tracking and available automation data for each connection.
Channel connectivity does not mean identical broadcast or automation capabilities. In-app messaging is distinct from mobile push notifications and in-game announcements.
Player support has a home.
Give proactive communication a process.
CXBOX HUB adds targeted messaging campaigns, tracked-link follow-ups and inactivity-based re-engagement around Zendesk. Gaming teams can organize announcements and connect replies with Zendesk customer service, using the audience records and channel data available to them.
Repeated announcements.
Teams share the same update across individual conversations and spend time keeping versions consistent.
Different players, different information.
A broad message can miss the needs of players interested in a particular game or language.
Questions need a clear next step.
Players reply to campaigns, but community and support teams still need to coordinate who continues.
Relevant news for
a clearly selected player audience.
Select contacts using recorded game interests, language or other available attributes. Share a season update, event information or getting-started guide through targeted messaging campaigns.
- Choose an audience from available records or a checked imported list.
- Prepare the announcement for that game and language.
- Give recipients a clear way to view details or ask for help.
Business value: reduce repeated information sharing and make announcements more relevant.
Game ownership, player level, spending and playtime are not inferred from messaging activity. Those attributes need an appropriate source before they can be used.
A player clicks for event details.
Send the related guide next.
Send a season update for the illustrative game Adventure Quest with a “View event details” link. When a recipient clicks that designated tracked link, click-based automation sends the related season event guide according to your settings.
1. Send the season update campaign.
2. Player clicks the designated tracked link.
3. Send the configured season event guide.
Business value: respond to a clear interest signal without checking each click and sending every follow-up by hand.
The tracked campaign-link click is the trigger. An initial inquiry does not trigger this workflow. A click does not register event participation or grant a reward.
Explain the service change.
Be ready for the player’s question.
Your team prepares a maintenance announcement with a date, time zone and support contact. A player asks: “Will support still be available?” Continue through your configured Zendesk player-support workflow.
- Check the announcement and audience before sending.
- Define how replies reach player support.
- Use Zendesk assignment to establish ownership.
Business value: keep information consistent and reduce coordination between the announcement team and support.
Switchboard conversation handoff is relevant where control must move between HUB, a bot or another conversation system and Zendesk. Direct inquiries already entering Zendesk can follow the existing process.
Create another conversation
around recorded game interests.
Configure “No interaction for 30 days” using supported messaging engagement history. Send a relevant game-news campaign to a selected audience through inactivity-based automation.
Business value: give your team a consistent way to reconnect without reviewing every contact history manually.
No messaging interaction does not mean the player stopped playing or is likely to leave. Login, gameplay, purchases and player-account information require their own data sources and connections.
Which player communication task
still takes repetitive manual work?
Tell us the game, audience, markets and channels involved. We will help assess one practical campaign and support workflow.
Add player engagement
around the Zendesk operation you know.
CXBOX HUB: outreach.
Use multichannel campaigns and configured follow-ups around selected player audiences. A ready-made app available on Zendesk Marketplace.
Zendesk: player support.
Continue individual questions in your Zendesk support process, with team and agent assignment handled there.
DEMETER: implementation.
Align channels, data and ownership through CX process design and Zendesk implementation services.
Measure the benefit: compare announcement preparation time, manual follow-up effort, available campaign clicks and replies, and time spent assigning follow-on conversations. Assess player retention or revenue only where relevant game and commercial data is available.
Define a focused rollout
before adding more markets.
1. Choose a use case.
Pick a season update, tracked-link follow-up, maintenance announcement or messaging re-engagement campaign.
2. Configure and test.
Confirm audience data, channel requirements, message content and how replies reach Zendesk.
3. Review the results.
Review team effort and available engagement signals. Refine the workflow before adding games, languages or channels.
Need game events or player-account data?
Account status, gameplay events, login history, purchases and automatic outage triggers require relevant data sources and an appropriate integration. Review integration requirements before confirming scope. In-app messaging also needs the relevant app setup.
Considering Zendesk? DEMETER can plan your player service journey and Zendesk implementation alongside the engagement workflow.
Gaming player engagement: FAQs
What does CXBOX HUB add to Zendesk for gaming teams?
CXBOX HUB adds targeted messaging campaigns, configured follow-ups after tracked campaign-link clicks and inactivity-based re-engagement. It connects proactive player communication with the service process handled in Zendesk.
Which channels can we connect for player engagement?
Channels include WhatsApp, LINE, Facebook Messenger, Telegram, Viber, X, Instagram and WeChat OA, alongside messaging in your mobile app through an appropriate setup. Campaign formats, outbound permissions, tracking and automation data vary by channel and connection. Confirm the workflow for each channel before launch.
Does mobile-app messaging include push notifications?
In-app messaging and push notifications are different capabilities. The workflow described here covers messaging conversations through the configured app connection. SDK work, push notifications and in-game announcements should be scoped separately rather than assumed to be included.
Can we target players by game, language or other attributes?
Use recorded attributes or a checked imported contact list. The data must be available and appropriate for the selected connection. Gameplay, player level, spending and account status need a relevant data source; HUB does not infer them from a conversation.
What triggers the event-guide follow-up?
The recipient clicks the designated tracked “View event details” link in the campaign. The configured workflow sends the related guide. An initial inquiry alone is not the trigger, and the click does not confirm registration, gameplay or reward eligibility.
Does inactivity mean a player has stopped playing?
No. The workflow uses supported messaging interaction or engagement data. Login and gameplay activity are separate data that require their own source and connection.
Do player replies always need Switchboard?
No. Direct inquiries already reaching Zendesk can use your existing service process. Switchboard is relevant when configured cross-system conversation-control handoff is required. Department and agent assignment remains in Zendesk.
Can we automate outage announcements or connect player-account systems?
This requires the relevant event source, player data, APIs and appropriate integration. The maintenance example on this page is team initiated. DEMETER can review your implementation and integration requirements before confirming scope.
How do we assess cost and business value?
Choose one repetitive communication task and review its audience, channel and reply process. Compare CXBOX HUB plans and pricing with the required configuration and implementation work. Measure manual effort and available engagement data before expanding.
Make your next player campaign
easier to run and support.
Already using Zendesk? Tell us which games, markets and messaging channels you support, what your team sends manually and how player replies are handled today.
We will help assess a focused Zendesk + CXBOX HUB starting point.
Explore CXBOX HUB or discuss Zendesk implementation and configuration with DEMETER ICT.