Already on Rewst? Here's where we fit.
Rewst automates your internal stack. Support Fusion syncs tickets across the boundary into a client's ITSM. Most IT service providers need both.
Two different jobs
Rewst works inside your administrative control
Your PSA, your RMM, and the client tenants you manage. You hold the keys, so Rewst can act across every environment you administer.
Support Fusion works across a boundary you do not control
When your client runs their own ServiceNow or Jira, you do not administer it. A governed, two-way sync where each side keeps its own control is what has to happen instead.
Where the line falls
These are the parts that make a cross-company sync hold.
Two-way state reconciliation
When both sides update the same ticket simultaneously, something has to decide which version wins and tell the other side.
Comment vs work note routing
A public reply and an internal note must not cross the boundary. Routing them correctly, both ways, is not a workflow step.
Status mapping and reopens
Your "Resolved" and their "Closed Complete" are different fields. The reopen path needs to hold on both sides.
Attachment streaming
Files need to move both ways, within each platform's size limits, between two organisations that each control their own storage.
A trust model for two companies
Each side needs its own credentials, scoped permissions, audit log, and a kill switch it can pull independently.
Rewst and Support Fusion at a glance
| Rewst | Support Fusion | |
|---|---|---|
| What it is | Automation and orchestration for IT service providers | Managed bi-directional ticket sync across company boundaries |
| Primary job | Automating work inside your own stack, across the clients you manage | Keeping a ticket reconciled across the boundary into a client's separate ITSM |
| Where it operates | Inside your administrative control | Across the boundary between two independent companies' platforms |
| Who builds the cross-company sync | You, in the workflow builder | It is the product |
| The client's experience | Works within the tools you administer | Client stays in their own ITSM and sees your tickets without logging into yours |
| Trust model | Built around one administrator | Each company holds its own credentials, scopes, audit log, and kill switch |
| Security posture | Rewst's own security programme | ISO 27001 certified, SOC 2 in progress. Credentials stay in each organisation's tenancy |
| Best fit | Internal service-delivery automation | The inter-company seam |
| Run them together? | Yes | Yes - different halves of the picture |
Better together
Run Rewst for internal service delivery, across the clients you manage. Run Support Fusion for the inter-company seam, where your tickets need to stay in sync with a client's ITSM. Neither requires removing the other.
Common questions
We already use Rewst. Do we even need Support Fusion?
Is Support Fusion a Rewst competitor?
Couldn't we build the client ticket sync as a Rewst workflow?
Which platforms does Support Fusion connect?
Connect your shop to your client's.
See how Support Fusion keeps your PSA and your client's ITSM in sync, without anyone having to be the glue.
Book a demo