Support Desk
Bring your own help desk
Replylume reads incoming tickets and writes resolution actions through each platform's native API. No separate inbox, no email forwarding.
Zendesk
Help DeskReads new tickets via webhook, resolves via Ticket API, updates status and posts resolution note.
Intercom
Help DeskConnects via Intercom webhooks. Replies to conversations and marks resolved with attributed note.
Freshdesk
Help DeskUses Freshdesk REST API. Reads ticket fields, updates status, and logs resolution activity.
Stripe
BillingRead-only charges API to verify orders. Refund write scope granted separately per configured limit.
Paddle
BillingSubscription and transaction lookup via Paddle API. Refund issuance within defined rule scope.
Salesforce
CRMWrites structured activity log entries per resolved ticket. Activity field scope only, no contact modification.
HubSpot
CRMCreates timestamped engagement records in contact timeline. Read-only on contact properties.
Webhook Architecture
How Replylume connects to your stack
Every action flows through a logged orchestration pipeline. Nothing is triggered without confirmation from the data layer first.
OAuth 2.0 for all integrations
Read-only billing scope by default
Every API call logged in audit trail
Use Cases
What teams actually run through Replylume
Refund resolution
Zendesk ticket arrives at 11pm. Replylume queries Stripe for order eligibility, issues the refund, sends customer confirmation, and closes the ticket. No human required for the 72% that meet rules.
Zendesk + Stripe + HubSpot
Order status replies
Customer asks "where is my order?" Replylume fetches shipping status from your billing system, replies with the current status and estimated delivery, closes or keeps open for follow-up.
Intercom + Paddle + Salesforce
Cancellation handling
Subscription cancellation requests that meet cancellation policy are processed via billing API, confirmation sent to customer, and CRM record updated with cancellation reason for CS follow-up.
Freshdesk + Stripe + HubSpot