Reviewer demo workspace

ChatGPT review demo guide

This page explains how the fake CRM workspace is prepared for ChatGPT app review. The demo workspace contains only synthetic CRM messages and does not require reviewers to connect a real WhatsApp account.

Purpose

The demo workspace gives OpenAI reviewers a stable way to test the ChatGPT app without using a real customer workspace, real WhatsApp account, SMS verification, or manually provided credentials.

Fake data only

No customer data is used in the demo workspace.

No login blocker

Reviewers can choose demo workspace from the OAuth page.

Real tools

The demo uses the same MCP tools as a normal workspace.

Seed data

The demo seed is idempotent. It creates or refreshes a dedicated installation, a connected fake WhatsApp session, three fake site groups, and ten fake CRM messages.

Local seed:
bun run --cwd apps/crm seed:chatgpt-demo

Production seed:
bun run --cwd apps/crm seed:chatgpt-demo:prod

Default demo installation id:
chatgpt-review-demo

The production seed uses `.env.production`. If needed, the demo installation can be customized with `CHATGPT_DEMO_INSTALLATION_ID` and `CHATGPT_DEMO_PROVIDER_ACCOUNT_ID`.

Reviewer steps

  1. Create a new app connector in ChatGPT.
  2. Set authentication to OAuth.
  3. Use https://whatan.app/api/chatgpt/mcp as the MCP server URL.
  4. Continue the OAuth flow.
  5. On the CRM page, choose Use demo workspaceif a real workspace session is not active.
  6. Return to ChatGPT and run the review prompts below.

Dataset

The seeded workspace includes these fake projects:

  • Demo - Palm Heights Site
  • Demo - Riverside Villas
  • Demo - Downtown Tenant Fitout

The messages include realistic CRM updates such as blockwork progress, electrical blockers, missing plumbing sleeves, cracked tile photos, drywall delivery, inspection status, and owner report requests.

Prompts

Suggested prompts:
1. List my WhatsApp conversations.
2. What happened today on Palm Heights?
3. Find messages with photos.
4. Find open issues from Riverside Villas.
5. Create a daily report for Palm Heights and save it.
6. Create a share link for the saved report.

The app should be able to read project messages, cite source message ids in saved reports when possible, save a document, and create a share link only when requested.

Maintenance

  • Run the seed script again any time the demo looks stale.
  • The seed is safe to rerun because it upserts the demo records.
  • Do not use real customer workspace ids for review.
  • Keep this page shareable by direct link, but avoid promoting it as public product documentation.