Quick often tries to send HTML-encoded email via the Outlook connector. It tells me the connector’s docs say it should be HTML.
It usually notices its mistake and sends a follow-up email to correct it.
It looks like a bug - perhaps the Outlook connector docs need updating?
The workaround is to remind it to send as plain text.
Hi @Tom_Kerswill ,
I think you’re right in that this is a quirk of how the agent interprets the connector’s tool schema. The Outlook connector maps to the Microsoft Graph sendMail API, which accepts both “Text” and “HTML” as the body content type. Quick sees HTML as a valid option in the tool docs and sometimes defaults to wrapping the body in HTML tags, especially for longer or formatted content.
A potential workaround could be to create a custom chat agent with the connector and add a line to your agent’s custom instructions like: “When sending emails via the Outlook connector, always use plain text format for the body content. Do not use HTML formatting.” That way it will ideally carry across all conversations without needing a reminder each time you use the chat agent.
That said, the underlying behavior (defaulting to HTML when the user didn’t ask for it) I think is worth flagging as a bug. I would recommend creating a support ticket and the support team will be able to further look into this. Please refer to this resource on how to create a ticket (Case management - AWS Support)