Four apps, two jobs they do well

Migrate your support history onto Zendesk, with sign-off at every step.

Migratron plans a migration in the open. It connects to your Salesforce org, an existing Zendesk, or CSV exports, analyzes what is actually in there, and walks you through field, account, user, and agent mappings one stage at a time. Nothing loads for real until a named approver has reviewed a live sample and said yes.

• Salesforce, Zendesk, and CSV sources — cases, accounts, contacts, agents, and whole comment threads, not just ticket headers.
• A guided workflow — connect, analyze, map, sample, load — where each stage is signed off before the next one opens.
• A real sample in your Zendesk that your reviewer walks ticket by ticket, with every approval and change request on the record.
• Migrate in phases, closed history first, so live cases move last and nobody loses a day to the cutover.

Turn the documents you already have into a Zendesk Guide worth reading.

Librarian reads your source material — PDFs, Word documents, or a knowledge base you already run — and proposes a whole Guide hierarchy: categories, sections, and article drafts, each with the reasoning for where it landed. You approve the structure, then the content, then publish into Zendesk.

• Reads the PDFs and Word documents you already have, or lifts the structure of a knowledge base you already run.
• Proposes the entire category → section → article tree at once, slotted into the shelves your Guide already uses.
• Two review gates — structure, then content — and the person signing off never needs a Zendesk seat.
• Publishes into Guide with your locale, permissions, and visibility rules, and can land everything as drafts first.

Branded support portals for your customers' vendors and partners, run from inside Zendesk.

Your support does not stop at your direct customer. Their vendors raise issues with you, their partners chase you for updates, and the people those partners serve end up in your queue as well. VendorApp gives each of those parties its own branded portal, running on the Zendesk you already operate.

• A branded portal per party, on its own subdomain or a custom domain, with SSL handled for you.
• Two parties on a ticket and never a third — a vendor cannot see what another vendor filed.
• One console for every portal: branding, organizations, users, and the Zendesk connection.
• Administered from inside Zendesk Support, with no second login for your team to keep.

Answer verified RCS messages in Zendesk, from a sender that carries your brand.

RCS is what replaced SMS on modern handsets: your name and logo instead of an unknown number, rich cards instead of 160 characters, and a verified badge that says the message is really from you. The Bridge carries those conversations into Zendesk, so an agent answers them in the same place they answer everything else.

• Two-way by default — a message from a handset opens a Zendesk conversation, and the agent's reply goes back to the handset.
• Your verified sender: brand name, logo, and colour on the handset, approved by Google and the carriers.
• Runs in your own AWS account, so the message traffic belongs to you rather than sitting in a vendor's system.
• The console tracks the registration — what is still missing, where the approval stands, and when it was last checked.