If Paddle is your merchant of record, the subscription and payment history should not live in another tab. Fernand shows them on the conversation and lets you automate from the same signals.
Included in our $29/human/month transparent pricing
The Paddle customer support integration is for SaaS teams who bill through Paddle Billing and answer customers in Fernand. After you connect your account, subscription, payments, and status show up in the conversation list and the sidebar.
That is enough to troubleshoot a failed payment or an incomplete transaction without bouncing to Paddle for every thread. It is also enough to build rules: a priority queue for a paid plan, or a slower auto-reply for free users.
Fernand supports Paddle Billing. Paddle Classic does not have the technical backbone for this integration.
Visualize the customer’s subscription, payments, and status from the conversation. Failed payments and incomplete transactions are visible without a tab switch.
Payment information populates on both the listing and the detail view, so you can spot a paying customer before you even open the thread.
Conditions include Contact is a customer (email matches a Paddle customer) and Contact has plan (matches a specific product name, like Premium or Business).
When a Paddle condition matches, a rule can reply, tag, assign (including round-robin), change status, or send a webhook.
The same payment signals can drive snippets, so a saved reply can behave differently for a customer on a paid plan.
If they write from a different email than the Paddle account, Fernand can suggest related customers across Paddle, Stripe, and Lemon Squeezy.
The failed payment is on the conversation. Your first reply can include the actual status instead of asking them to forward a receipt.
A rule or a split inbox on Contact has plan (your paid product) keeps those conversations visible. This is the same VIP pattern that works with Stripe and Lemon Squeezy.
Auto-reply when Contact has plan matches your free product, and tell them you usually get to those requests later. Paying customers are unaffected.
This integration is Paddle Billing only. If you are still on Classic, you will need Billing before Fernand can show native payment data.
Fernand looks up the contact against Paddle. When it matches, billing context is attached to the conversation automatically.
Plan and payment status sit in the sidebar of the shared inbox. Fernand AI can use the same context in drafts.
Once the data is there, you are not triaging by memory. Conditions on customer and plan drive tags, assignment, and replies.
You can connect Paddle Billing during the trial with no extra limitation. Disconnect anytime from the Integrations page.
Straight answers, without the marketplace filler.