What to ask

Once your AI app is connected, ask in your own words. These requests work well, and the tips below help the AI get it right the first time. They work for the in-app assistant too.

Say which diagramCopy Anchor Link

The AI works on one diagram at a time, and every change names it by its id.

• "this diagram" means the one open in the app. The AI checks which one that is.
• Name it to work on another: "the purchase request diagram".
• Ask for a new one with a name: "Create a diagram called Expense claim."

To watch while the AI works, ask it to open the diagram in the app first: "Open the onboarding diagram and add a background check."

Draft a new processCopy Anchor Link

Give the AI the facts it can't guess. A good request says:

• Who's involved. These become lanes: "employee, manager and finance".
• What starts it. "When an employee submits a claim."
• The outcomes. "Paid, rejected, or sent back for changes."
• The rules. Thresholds, deadlines and SLAs: "Claims over 500 EUR need a director", "Remind the manager after two days."

For example:

Create a diagram called Expense claim. An employee submits a claim with receipts.
Their manager approves it, rejects it or sends it back for changes. Claims over
500 EUR also need a director. Finance pays approved claims. Remind the manager
if they haven't decided after two days.

For a common area, ask the AI to look up the guidance first: "Look up the guidance for procure to pay, then draft our process." The app has reference processes for areas such as order to cash, recruitment, incident management and loan origination. See Guidance topics for the full list.

If you leave out the essentials, the in-app assistant may ask a few short questions first. To skip them, say "draft it now and list your assumptions".

Change an existing diagramCopy Anchor Link

Point at the step and say what should change:

• "Add a credit check before approval in the loan diagram."
• "After Review request, add a reminder if it takes more than two days."
• "Move Pay expense to the Finance lane."
• "Show the supplier as an outside party, and the purchase order we send them."

For small changes the AI edits only what you asked about, so the rest keeps its ids and stays as it was. If you want the whole process reworked, say so: "Restructure this diagram around three lanes."

Review, fix and explainCopy Anchor Link

• "Fix the problems the checks report in this diagram." The AI gets the same modeling checks you see after every change. It fixes what is plainly broken and keeps the rest as it is. When a fix depends on what you meant, such as a step connected to nothing, it asks you first.
• "Review this diagram against BPMN practice. Suggest changes, but don't make them yet." The AI reads the diagram and answers without changing it.
• "Explain this diagram in plain words for a new starter."

Draw a sequence diagramCopy Anchor Link

Say it's a sequence diagram when you ask for a new one: "Create a sequence diagram called Checkout payment." Then say who takes part, what starts the interaction and which failure paths matter:

Create a sequence diagram called Webhook delivery. Our shop puts an event on a
queue, a worker posts it to the customer's endpoint and retries up to 5 times
with backoff. After the last failure it moves the event to a dead-letter queue.

Changes work the same way: "Add a cache in front of the database in the orders API diagram." See The assistant for sequence diagrams for more.

Steer the resultCopy Anchor Link

• Name what you mean exactly. Use the names on the diagram: "Review request", not "the review step".
• Say what to leave alone. "Don't change the Finance lane."
• Ask for one level of detail. For a large area, ask for a call activity that stands for it, and model the detail in its own diagram.
• Ask for notes. "Add a note on Review request: SLA 2 working days."

The AI can't place shapes or change the look of the diagram. The app lays out every diagram the same way, whoever changed it.

If something goes wrongCopy Anchor Link

Every change the AI makes goes into the diagram's version history, and the app's Undo takes back changes that came from your AI app too. If you and the AI change the same diagram at the same moment, its change is refused, and it's told to read the diagram again and retry.