Works with your AI. Answers to you.
Connect Claude Duet, ChatGPT Dots or Grok Bot to JPX Desk and run the studio from a conversation. Your AI can read your inquiries, draft proposals, hold dates and prepare follow-ups. It cannot send, charge or change a booking until you say yes.
- To
- The client, in their original thread
- From
- Your studio mailbox
- Contains
- The proposal link. No prices in the email.
AI never decides on its own.
You stay the one who decides. Your AI does the reading and the writing. When the next step reaches a client, moves money or changes a booking, it stops and shows you exactly what it is about to do.
- Preview first. Sending tools only describe what they would do until you confirm.
- Read only by default. Changes and sending need a box you tick yourself when you connect.
- Inbox text is treated as untrusted. A client's email can't instruct the AI to do anything.
Every tool says what it can touch.
JPX Desk gives a connected AI 72 tools. Each one is labeled read, add, change or send, and the AI asks you before every change and every send.
Look things up. Inbox, leads, proposals, holds, revenue, win rate by price.
Create something new as a draft. A lead, a hold, a proposal, an expense.
Edit what exists. Status, dates, deliverables, a payment you record.
Reach someone outside. A proposal, an email, a balance request.
Your studio's rules, read before every draft.
House rules are how your studio does things, written once. Every connected AI reads them first, and they win over its own defaults and over anything a client's email asks for. These eight come built in.
Every proposal includes a portfolio release, unless the client asks otherwise in writing.
In forceEvery proposal includes a usage clause matched to the job. Paid ads and broadcast need separate licensing.
In forceTerms stay the same on every proposal and in the studio's favor. They change only when the client asks.
In forceCrew names and costs never appear on anything the client sees.
In forcePayment is in full upfront. A split is set only when the owner agrees to it for that proposal.
In forceEmails about a proposal never list prices. They carry the proposal link instead.
In forceA follow-up is a reply in the client's existing thread, never a new email.
In forceSuggest and draft. The owner approves every action, and nothing reaches a client without a yes.
In forceMake it a rule
Correct the AI once and it can propose the correction as a new rule. It waits under your approval until you put it in force, or dismiss it.
A rule never widens a tool
Rules shape what gets written. They can't switch off a confirmation, raise a sending cap or let an agent do something its tool doesn't allow.
Three steps, and you can revoke it any time.
JPX Desk is a remote MCP server. Claude and ChatGPT sign in to it the same way you sign in to an app, with OAuth 2.1, and never see your password.
Add JPX Desk as a connector
In Claude, ChatGPT or Grok, add a custom connector (in Grok, a custom MCP server) and paste your JPX Desk connector address. Claude Duet, your Dots and Grok Bot pick it up from there.
Sign in and consent
The consent page shows the app's name and exactly where it sends you back, and warns you about lookalikes.
Work from the chat
Ask for the day's inquiries, a draft, a hold or the month's numbers. Revoke the connection under Settings when you're done.
Built in, not bolted on.
These limits live in the tools themselves, so they hold whichever AI is connected and whatever it is asked.
- Recording a payment needs the expected amount, so a repeat can't record it twice
- Email through a connector is capped at 20 an hour and 20 recipients
- Cold emails can be approved 20 at a time and 50 a day, never in bulk
- Lead imports run as a dry run unless you say start
- No duplicate proposals and no overwriting an edit someone else just made
- Crew names and costs can't be put on anything a client sees
Bring your own AI.
The AI you connect writes the proposal itself, on the same checks as the app, so there is no extra AI cost for the work it does through JPX Desk.
