SUPPORT WRITING GUIDE

Using ChatGPT with Gorgias: manual transfer or a draft-connected assistant?

Compare a manual ChatGPT rewrite with a draft-connected workflow. Trace what you transfer, where you review and who updates the reply in Gorgias.

A handoff ledger for one fictional draft

Start. Both paths begin with the same checked draft in Gorgias: “I can check the repair status on Tuesday. I do not have a confirmed completion date.” Tuesday is for checking the status, not completing the repair.
Transfer. Manual: confirm your team permits the account and the text, then copy only the approved draft excerpt to ChatGPT. Draft-connected: check the required workspace and extension access, then request a wording suggestion on the draft you already wrote.
Review. Manual: read the response in ChatGPT before bringing any wording back. Draft-connected: compare the Vellix suggestion with your original before choosing to apply it. In both cases, reject wording that turns a Tuesday status check into a Tuesday repair promise.
Return and send. Manual: paste the approved wording into the intended Gorgias composer. Draft-connected: deliberately apply the whole replacement and check that it reached the intended composer. In both paths, the agent checks the final reply and decides whether to send.

Decide what can move

Before you copy anything, establish which account, tool and draft text your team permits. If you cannot confirm those permissions, edit the draft directly. A connection to the composer is not evidence about what a service receives or retains. Check those terms separately for any tool you evaluate.

For a manual rewrite, OpenAI recommends giving ChatGPT a clear task and reviewing its response. With the fictional excerpt above, you might ask: “Make this reply easier to read. Keep Tuesday as the day I check the status. Leave the completion date unconfirmed.” That is an example instruction, not a sample model response.

Check the draft where it will be sent

Gorgias distinguishes an internal note from a customer reply through the composer’s channel selector. After pasting or applying a rewrite, confirm the ticket and reply channel. Read the whole draft in that composer, including any links, formatting and commitments. A suggestion in another window does not tell you what is in the send box.

If you try both paths, record where you reviewed the wording and what you did to put it in the composer. If you cannot account for a transfer or confirm the final text, keep your checked draft and edit it manually.

Try the review and replacement step in Gorgias

Vellix offers a wording suggestion on an existing Gorgias draft. Read the whole suggestion against the original. If you choose to apply it, Vellix replaces the whole draft in the composer. This is a separate workflow from manually transferring text to ChatGPT.

Check the setup requirements before a trial. You need access to the Gorgias workspace and the Chrome extension, plus available trial or API-key access as applicable.

You verify the facts and the promise, confirm the ticket and channel, read the final composer and decide whether to send.

Try one permitted routine draft with a specific update promise. See whether the suggestion preserves that promise and whether you can confirm the whole replacement in the correct composer.

See setup requirements

Sources and editorial note

Examples are fictional. Sources for the platform guidance are linked below.

OpenAI guidance on giving ChatGPT a specific task and reviewing the result. Checked 2026-11-06.
Gorgias documentation on the composer, reply channel and send controls. Checked 2026-11-06.

Keep reading

All writing guides