A few questions.
Clear answers.

TruCom brings the work of customer support into one workspace: a shared inbox, website live chat, connected messaging channels, tickets, help content, AI assistance, automations, service updates and customer feedback.

Your team can answer a question, keep track of the follow-up and give customers a clearer way to find help or understand what is happening. Choose the tools and capacity that fit your work and plan.

Yes. You can begin with one channel and a simple agreement about who picks up each request. Add help articles, ticket follow-up or rules when they solve a task your team actually has.

Compare the seat allowance and tools on each plan with the people who need access. You can organise departments and teammate permissions as responsibilities grow.

Create a workspace, bring in the people who will answer and connect one channel your customers use. Prepare a few useful answers, then send a test question as a customer and reply from the inbox.

Try a handover and a question that needs more time. That small test helps you check ownership, notifications and the customer’s next step before adding more to the routine.

You need access to add TruCom’s widget code to your website. If your website has a place for custom code, you may be able to add it yourself. Otherwise, share the installation instructions from your workspace with the person who manages the site.

After installation, open the website on a phone and a computer, send a message and check that it reaches the intended team.

You can use website live chat and connect supported WhatsApp Business, Instagram Professional, Facebook Page Messenger and Telegram accounts or assets.

Each connection has its own account, permission and activation requirements. Start with the channel options page, then follow the setup in your workspace and test a message from the customer’s side.

You can connect an eligible account or asset that you have permission to authorise. The requirements differ: Page messaging needs the appropriate Facebook Page access, Instagram needs a Professional account, and WhatsApp needs an eligible business account and number.

Telegram bot and authorised profile or chat connections have their own permissions too. Review the selected account carefully before activating it.

Messages received through an active, authorised connection can appear in the shared inbox, with the content and context that the channel provides. The connection applies to the account, Page, number, bot or chats you have authorised.

Check the supported message types and account requirements for that channel. An active connection does not mean that every historical message or every private chat in the account has been imported.

Open the connection in Settings → Channels and review its status, selected account, department and any activation or permission steps it shows. Complete the required authorisation, then test a new message from another account.

If access was removed or the provider requires another approval, follow the connection’s instructions. Keep the channel’s reply requirements in mind when testing a response.

Assignment gives a conversation a responsible teammate, while departments help organise the work for the right group. The inbox keeps the message history and available customer context with the request.

Agree how your team picks up unassigned work and when to hand it over. The person taking over should be able to understand what has happened and what they need to do next.

Use a ticket when an issue needs a tracked next step beyond the immediate exchange: an investigation, a task for another department or an update that will take more time.

A conversation can lead to a linked ticket, so the follow-up has its own status, priority and assignee. Tell the customer what happens next and how they can check back.

Yes. Internal notes let your team record context for colleagues. They are separate from customer-facing replies.

Use a note for the detail the next teammate needs: what you checked, what is still unclear and who owns the next step. Check whether you are writing a reply or a note before sending it.

Rules can handle supported steps such as assigning work, changing a status or priority, adding tags and notifying an internal recipient. A trigger starts the check, conditions decide what matches, and actions set out the next steps.

Choose one clear purpose and use a dry run to check it against real workspace records before enabling it. The automation guide shows how All and Any conditions affect which tickets are included.

The AI support agent can answer eligible customer questions from the knowledge you enable for it. Its operating mode and connection settings determine where it can help.

Agent Copilot supports the teammate doing the work, with reply suggestions, summaries and related knowledge. A teammate reviews a suggested reply before using it. Availability and usage depend on your workspace’s plan, settings and AI access.

TruCom searches the ready, AI-enabled knowledge sources available to the task and audience. Clear, current help content gives it something useful to work from; a source being uploaded alone does not make it ready for answers.

Prepare the content, check its audience and AI access, then test questions in the Playground. Try both questions the content should answer and questions that need more information or a person.

Yes. A customer can ask for a person, and an AI conversation can request a human handoff when the available knowledge is not enough. AI pauses for the handoff so an eligible teammate can continue with the history in view.

Make sure the intended team can receive these requests. A handoff asks for human help; when someone can pick it up depends on your team’s availability.

No. You choose the intended audience and visibility for your content. Customer-facing answers need knowledge appropriate for customers, while team guidance can support agents in their work.

Public article visibility and AI access are separate choices. Check the source’s audience, readiness and AI setting before relying on it in an answer, and test the result from the customer’s side.

Yes. Published help articles give customers answers they can find for themselves. Your support centre can bring help and ticket follow-up together, so people have a place to return to.

For service health, direct them to your status page. For product ideas, use your feedback and roadmap page. Make the right destination easy to find from your website and replies.

Use your status page to explain affected services, share incident updates and communicate maintenance. Monitoring can help your team notice supported service checks that need attention.

Write updates people can understand: what is affected, what your team knows and what they should expect next. Review an automated signal before treating it as the full explanation of an incident.

A request records an idea or need; it is not a delivery promise. Your team can organise feedback, review the support behind it and use roadmap stages to show the progress you choose to share.

Keep the wording of those stages clear. Customers should be able to tell whether an idea is being considered, worked on or has been delivered without having to guess.

Yes. TruCom has mobile layouts for working from a phone, alongside the desktop workspace. On a supported device, you can also install it from the browser and open it from your home screen or app launcher.

Try the tasks your team relies on, including opening a request, replying and checking follow-up work. Browser and device support determine the installation options you see.

The plan price is for one workspace. Each plan lists its included team seats, tools and usage allowances, so compare both the people who need access and the work they will do.

Use the published pricing page for the current options. Your workspace’s billing area shows the subscription and usage that apply to your team.

We use an approximate country estimate to look for published local pricing. Where a local price is available for the plan and billing interval, we show it; otherwise, we use the published USD price.

You can change the country on the pricing page if the estimate is wrong. Local prices are set separately rather than converted with a live exchange rate. Check the currency shown with each amount and confirm the billing details in your workspace before subscribing.

You pay the full yearly amount shown for that plan and currency. When a published yearly price offers a saving against twelve monthly payments in the same currency, the pricing page shows it.

The payment interval and usage reset cycle are separate. Paying yearly does not turn a monthly usage allowance into one annual allowance; check the cycle listed on the plan.

Yes. Review an upgrade or downgrade in your workspace’s billing settings. The confirmation shows any amount due and when the change takes effect before you continue.

Check the new plan’s seats, features and allowances against what the workspace already uses, so your team understands the effect of the change.

AI availability and included credits depend on the plan. Different models and operations can use different amounts; your workspace shows the balance and any available top-ups with their prices.

If a plan offers a trial, its length is shown with the plan. Review the published allowances and your workspace’s AI settings before deciding how much of the support routine to enable.

The prices on TruCom’s pricing page cover the TruCom subscription. A connected service may apply its own charges and account requirements.

Check the provider’s terms for the account and connection you are using, alongside your TruCom plan. The channel setup page explains the requirements for connecting each service.