# Post-payment care and support cases

After a sale, a customer's problem becomes a support case, whichever channel it arrives on. The case ends with the customer: once a resolution is verified and the notice has gone out, the customer's rating closes it, and a reply saying it is still broken reopens it. Every stage shows its time and the evidence behind it.

- **Status:** Available
- **Audience:** both
- **In the app:** /apps/crm (Customer Care cases)
- **Last verified:** 2026-11-02
- **Canonical:** https://connectbyjbrh.com/docs/product/post-payment-care/

## The nine stages

1. Identify
2. Record
3. Acknowledge
4. Investigate
5. Resolve
6. Verify
7. Notify
8. Customer review
9. Close

Each stage is read from the case's own audit rows, so the lifecycle shows what happened and when. It is never a status someone typed. The Notify stage reads *notice sent*, with its time, only after a reply on a verified-resolved case has actually left.

## How the customer closes or reopens a case

Connect reads a rating from the customer's own words, such as "5/5", "4 out of 5" or "rating: 3". A message saying it works, with a rating, closes a resolved case. A message asking for changes reopens it. An unresolved case cannot be reviewed, so a rating cannot close something nobody fixed.

The same handling applies on email, WhatsApp and phone, because it works on the customer's message rather than on a channel.

## Platform defects and your own features

A problem in Connect itself follows JBRH's engineering pipeline, which is unchanged. A request for a feature only your business needs follows a separate path: see [features for one business](/docs/product/custom-features/). Resolved items JBRH approves may appear on the public [Product updates page](/docs/product/product-updates-page/), without private details.

## Where you find it, and who sees what

Cases live in the CRM app's Customer Care area, with the lifecycle on each case. The Owner and a customer business use the same screens and the same rules, each for their own customers, and neither can see the other's cases. A case keeps its full history, including every reopening, so a support lead can see how often a fix did not hold.

The customer's rating stays with the case as part of its record. A business can read the ratings for its own cases, and nothing is published unless JBRH approves a resolved item for the public updates page. Even then, the customer's private words are not shown.

## What is not yet verified

- The phone and WhatsApp legs were proved through the channel-neutral functions on a test workspace, not through a real call. A live call is the owner's own check on their own authorised phone.
- No calling setting, voice or prompt was changed for this.

## Questions

### Can a case close without the customer?

A resolved case waits for the customer's review. Their rating closes it, and their report that it still fails reopens it.

### Does the channel matter?

No. The same rules apply to a message on email, WhatsApp or a call, because they work on what the customer said.

## Related

- [Support cases](https://connectbyjbrh.com/docs/support/cases/)
- [The relationship after the sale](https://connectbyjbrh.com/docs/support/post-sale/)
- [Resolving a case](https://connectbyjbrh.com/docs/support/resolving/)
- [Features for one business](https://connectbyjbrh.com/docs/product/custom-features/)

## What this page is based on

- `backend/app/autoops_client_support.py`
- `docs/agents/tasks/s4-care-feedback-20261102.md`
