Build your own support experience
Use TruCom behind your own website, portal or mobile app.
Your interface, one connected support operation
Build the screens your customers see in your own brand. Your backend connects those screens to TruCom’s customer profiles, tickets, public ticket replies and feature requests. Your support team can continue working from the workspace.
Keep REST keys on your backend. Your website or native app calls your authenticated application endpoints; your server authorizes the customer and calls TruCom. A JavaScript widget remains optional for these API flows.
A practical customer journey
After sign-in, resolve the customer from a stable external_id using the customer lookup or upsert endpoints. Store the returned customer ID against that authenticated account.
Open a ticket from your own support form. Show that customer’s ticket list and status in your app, then fetch public replies. Submit later customer replies through the ticket reply endpoint.
Collect suggestions with the feature-request endpoint. Show the customer their own submissions and status changes. Fetch published public requests for a branded ideas board, while keeping private requests visible only to the people your application authorizes.
Authorize each customer on your server
API keys grant workspace access according to their scopes. Derive customer_id from your authenticated application account and check record ownership before returning ticket data or replies. Do not expose a general workspace API proxy to unauthenticated visitors.
Use the same Idempotency-Key when retrying a timed-out create or reply operation. Follow the next cursor for lists and retain X-Request-Id when investigating a failure.
Keep your integration visible
Settings / API access / Request log shows request times, endpoint templates, status codes, durations, key attribution and request IDs. Open a row for byte counts, error codes and replay status. Filter by key, outcome, UTC dates or request ID.
Logs record request metadata rather than credentials, headers, query values or message bodies. The default retention is 30 days. Requests with a matching key can still be recorded when that key has expired or been revoked.