# Fictional account brief: Mossbridge Demo

**Synthetic example.** The organisation, people, records and events below are invented. This is a manually authored illustration of the brief format. It demonstrates neither live source retrieval nor AI-generated accuracy. No real customer information is used.

## Meeting

- Account: Mossbridge Demo, fixture account DEMO-001
- Purpose: Agree a measurable adoption goal and an owner for the next review period.
- Date: 27 October 2026, 10:00 Europe/Helsinki, according to S1. S2 records 28 October; the organiser still needs to confirm the date.
- Account owner: Customer Success lead (fictional role)
- Confirmed attendees: Customer operations manager and account owner, per S1
- Invited but unconfirmed: Customer operations director, per S1
- Prepared at: 23 October 2026
- Review status: Draft. Account-owner approval pending.

## Read before the call

The last review agreed that the customer operations manager would propose an adoption goal, but the current note does not contain that goal [S3]. An integration-mapping issue remains open in the supplied support snapshot [S4]. Confirm its business impact and agree the next review's goal and owner.

## Confirmed context

| Observation | Source | Record date | Last checked |
|---|---|---|---|
| An adoption review is scheduled for 27 October at 10:00 Europe/Helsinki | S1 | 22 Oct 2026 | 23 Oct 2026 |
| The operations manager is confirmed; the operations director has not accepted | S1 | 22 Oct 2026 | 23 Oct 2026 |
| The last review recorded a commitment to propose an adoption goal | S3 | 14 Oct 2026 | 23 Oct 2026 |
| The integration-mapping case was open at the time of the supplied snapshot | S4 | 22 Oct 2026 | 23 Oct 2026 |

## Previous commitments

| Commitment | Recorded owner | Due date | Status | Source |
|---|---|---|---|---|
| Propose an adoption goal before the next review | Customer operations manager | Exact date not recorded | Completion unconfirmed | S3 |
| Send the mapping example needed for investigation | Account owner | Exact date not recorded | Support snapshot says received on 21 October | S4 |

## Hypotheses to check

- The mapping issue may be making adoption harder. S4 establishes an open case, but not its impact on usage or the customer's goals. Ask the customer what work it affects.
- A broader rollout may still be under consideration. S2 says it was discussed, but there is no confirmed expansion plan, date or commercial commitment.

## Missing information and conflicts

- Meeting date: S1 says 27 October; S2 says 28 October. Use the current invitation as the working schedule and ask the organiser to confirm it.
- Adoption goal: S3 records the commitment, not the completed goal. Ask the operations manager for the proposal.
- Case status after 22 October: The snapshot cannot establish whether the case was resolved later. Check with the case owner before the meeting.
- Renewal date: Not included in the fixture. Do not infer a renewal deadline or churn risk.
- Product usage: No usage records are supplied. Do not claim an engagement decline.

## Questions for the meeting

1. What work is the mapping issue affecting today, and what would an acceptable resolution look like?
2. Which adoption goal should the next review measure, and who will own it?
3. Is a broader rollout still being considered, and what would need to be true before deciding?

## Proposed next action

Agree one adoption measure and its owner during the meeting. Confirm the support case's next step with its owner. Record the agreed review date after checking availability.

These are proposals. The example does not imply the customer has accepted them.

## Synthetic source register

| ID | Fictional record | Reference | Record date | Last checked |
|---|---|---|---|---|
| S1 | Calendar invitation | DEMO-EVENT-001 | 22 Oct 2026 | 23 Oct 2026 |
| S2 | CRM account note | DEMO-CRM-001 | 20 Oct 2026 | 23 Oct 2026 |
| S3 | Previous review notes | DEMO-MEETING-001 | 14 Oct 2026 | 23 Oct 2026 |
| S4 | Support case snapshot | DEMO-CASE-001 | 22 Oct 2026 | 23 Oct 2026 |

[Download the synthetic source records](/downloads/account-research-input.json) to check this example. The references above are fictional IDs, not links to customer systems.

## Human review

The account owner must confirm the schedule and case status, verify the source references and approve this draft before use. The example includes no completed review or meeting outcome.