> Source: https://mywaypoint.ai/docs/ask/catch-up-on-a-case
> Documentation index: https://mywaypoint.ai/llms.txt

# Catch up on any case in one question

**Give Chip a case number & it reads the support thread, the engineering ticket linked to it & every comment on both, then answers the specific thing you asked with the summary & the current status behind it.**


## For

- [For Support](https://mywaypoint.ai/for-support)
- [For Revenue](https://mywaypoint.ai/for-revenue)
- [Support Engineering](https://mywaypoint.ai/use-cases/support-engineering)

## In

- [Salesforce](https://mywaypoint.ai/docs/integrations#salesforce)
- [Zendesk](https://mywaypoint.ai/docs/integrations#zendesk)
- [Slack](https://mywaypoint.ai/docs/integrations#slack)
- [Jira Cloud](https://mywaypoint.ai/docs/integrations#jira-cloud)

## Use case

```prompt-request
Can you summarize case 00274318 for me? What error did engineering find in the logs, and where does it stand now?
```

## What Chip did

Chip went straight to the case & loaded everything attached to it: the customer conversation, the engineering ticket, the comments on both, the labels & fields & the earlier cases already linked to it as related.

## What came back

- **The error engineering found**, quoted from the ticket, with the link.
- **The story so far**: first report, what was tried, what changed, in order.
- **Where it stands**: the status of the case & of the engineering ticket, with who has touched it.
- **Suggested follow-ups.** Whether other customers have hit the same error, what fixed the closest earlier case, what is left on the engineering ticket.

**What you have now.** The whole case in one answer, ready before the customer call. The follow-ups are the questions the customer is about to ask.