Skip to main content
After you open a dispute, LiftAI drafts the vendor email for you. You review and edit it, then send — and the dispute starts waiting on the vendor. This is the second step in the dispute funnel; the next is tracking the vendor’s response.

​
The AI draft

When you open a dispute (or ask for a follow-up or a data request), the agent generates an email draft pre-filled with:
  • To and CC recipients
  • Subject
  • Body
  • Contract citations drawn from the AI invoice review findings — the contract sections and quotes that back up the disputed charge, listed under Contract Citations as “Referenced in this email.”
There are three kinds of draft: a dispute email, a data request, and a follow-up. An agent-generated draft is marked with an AI Draft badge so you can tell it apart from anything you’ve edited.
The From address is read-only. Dispute emails are always sent from LiftAI’s shared sender address, so it isn’t something you set on the draft.

​
Edit, attach, or discard

1

Edit any field

You can change the To, CC, Subject, and Body directly in the draft editor before sending.
2

Check the attachments

The invoice’s own attachments are included by default so the vendor sees the document in question. Both the draft attachments and the invoice attachments are listed in the Attachments section.
3

Discard if you don't want to send

Use Discard to throw away the draft. Discarding clears the draft from the panel and returns the dispute to its prior state.

​
Send the email

When the draft looks right, send it.
1

Send

Sending delivers the email to the vendor and moves the dispute to Awaiting Vendor.
2

The panel enters a monitoring state

Once the dispute is awaiting the vendor, the panel polls for a reply and shows a Monitoring indicator with “Waiting for vendor response.” You’ll get a success confirmation when the send goes through.
Replies route back to LiftAI automatically. Each dispute has an encoded reply-to address, so when the vendor replies the message is matched to this dispute and appears in the timeline without any forwarding on your part.
If a send fails, the panel surfaces the error (for example, in a notification) instead of silently dropping the message. Fix the issue — often an invalid or missing recipient address — and send again.

​
Next steps