The quotation summary looks correct in the sender's preview. In the recipient's chat tool, however, an optional charge appears beside the main price, a condition is separated from the amount it qualifies, or formatting characters become visible text. The numbers may all have survived. Their relationship may not have. That makes message formatting a commercial communication issue, not just a choice of visual style.

On October 16, Google announced an app-level default markup-syntax setting for the Chat API, with standard Markdown and the original Chat syntax as options and a request-level override. The change is relevant to applications using that interface. It does not establish a universal format across messaging products or require existing integrations to change their defaults immediately.

Keep the business fields separate from their presentation

A model identifier, quantity, currency, unit price and qualifying condition are distinct pieces of information before they become a message. Preserve that distinction. If the only retained version is a formatted text string, forwarding it to another tool asks the next renderer to reconstruct meaning from symbols that may have a different purpose there.

Some failures are obvious, such as visible markup or a broken link. Others leave all the words intact but change their relationship. A line break can separate a price from its unit; a list can lose the grouping between the base machine and optional accessories. Symbols inside identifiers may also need escaping under the destination syntax. Check the copied identifier against the source instead of judging it only by appearance.

For a team working with Chinese manufacturers, the practical response is to generate each destination message from the same underlying fields. The chat summary can stay short while pointing to the versioned quotation or product record for detail. It does not need to reproduce every contractual term, but a condition necessary to understand the amount shown should not depend on knowledge held only by the sender.

This also separates a format repair from a commercial revision. Fixing a line break should not cause an AI assistant to reinterpret a pricing rule. Shortening a notification should not remove a unit because the model considers it repetitive. If the amount or product condition needs to change, handle that as a content decision. If only the renderer changes, preserve the approved meaning and change the presentation deliberately.

One chat product can contain more than one rendering surface

Google's current formatting guide distinguishes text-message formatting from text inside cards. That is a useful warning against treating an application as one uniform canvas. A string prepared for a message body may not be appropriate for a card field, even before it is forwarded to an entirely different platform. The destination object matters as well as the application name.

Before changing an integration's default syntax, inspect whether existing requests specify their own syntax and which message types they create. A shared default can affect older notifications that nobody included in the first preview. Changing the default is not a content migration plan, and there is no need to resend historical quotations simply to test how a new renderer behaves.

Instead, use a small set of non-sensitive examples containing the features that matter: a model with meaningful separators, several cost items, a long product link and an explicit quantity condition. Read the result in the intended receiving surface. Then copy the model and open the link. These checks distinguish something that merely looks plausible from something a buyer can actually use to identify the product and continue the conversation.

The same checks should include the relationship between fields. Can a recipient tell whether a fee is optional? Is the amount per item or per set? Does a qualifying statement remain beside the relevant claim? Our article on defining the arithmetic before building an AI quote calculator addresses the meaning of the calculation. Message rendering needs to preserve that meaning after the calculation leaves its original tool.

When an overseas partner adopts a new messaging product, the supplier should not need to rewrite the underlying product facts. Keep a stable source record and a small set of destination examples. Adapt the display to the new surface, while changes to prices, units or product identifiers remain separately reviewable. That separation makes mistakes easier to locate without turning every visual correction into another round of commercial approval.

A quotation summary has done its job when the recipient can identify the priced object, understand the necessary conditions and reach the correct supporting material. The sender's editor is only the starting point of that check. The receiving view is where the message finally acquires its practical meaning.

Sources