Customer-support workflow automation

Automate recurring support work, starting with one process.

Pronomy helps growing B2C teams handle cancellations, refunds, and subscription changes. We scope the account checks, company rules, and permitted actions with your team, then validate the workflow before release.

See a refund example Download overview 1 page · PDF
Have a client in mind?

Guided refund example

See the request, checks, and next action.

Interactive example · sample data · no real accounts are changed.

Customer message

“I was charged yesterday. Please refund the payment and stop my subscription from renewing.”
Payment
$29 · yesterday
Request
Refund + stop renewal
Environment
Illustrative sample only

How the example works

  1. Request: identify the account and requested actions.
  2. Check: verify identity, payment, history, and the sample policy.
  3. Act: refund the sample payment and stop renewal when permitted.
  4. Result: confirm the outcome, or hand an exception to a person.
Ready to start Approved path
  1. 1Request
  2. 2Check
  3. 3Act
  4. 4Result

Ready when you are

Walk through one approved example.

Nothing runs automatically. Use the controls to see each decision in order.

See what was checked
Account

Identity is confirmed for the approved path. The alternate path stops when it is not.

Payment

The $29 payment was yesterday, with no prior refund or dispute in the sample.

Sample policy

Refunds within 30 days are permitted after the checks; refund and stopping renewal are approved for this example.

Fit and boundaries

Could this fit your team?

  • Similar requests arrive repeatedly.
  • The team follows identifiable rules and checks account data.
  • Someone can review the process and decide which actions are allowed.

A scoped engagement

Start with the process, not a platform rollout.

Recommended starting shape; final scope is agreed after review.

Shareable capability summary

A short overview to share.

What Pronomy helps automate, who it fits, and how to start a scoped conversation.

  • Typical work: cancellations, refunds, subscription changes.
  • Starting point: one recurring process with clear rules and an owner.
  • Delivery scope: agreed after reviewing systems, permissions, and expected outcome.

Partners and referrals

Have a client in mind?

Tell me what their team handles repeatedly and which systems they use. We can review the fit and discuss how to work together.

Share a potential workflow

Partner roles and commercial terms are agreed separately.

Which systems are involved?

That depends on the selected process. We review where account data lives, what permissions are available, and which action needs to be completed before defining the integration scope.

What happens when information is missing?

The workflow stops before an uncovered action and passes the case to a person with the available context and the reason it could not continue.

How are implementation and pricing decided?

They are confirmed after reviewing the process, systems, permissions, responsibilities, and expected outcome. They are documented in a client-specific proposal.