Last verified: October 11, 2026
What You Can Now Do
Context Memo customers can now set guardrails, enable voice, and configure a daily budget limit for their Chat feature in the Chat settings panel. All three are live and configurable by you, not by us on your behalf. The practical change is that Chat behavior and Chat cost are now settings rather than defaults. If you have been keeping Chat limited to a small internal group because you could not bound what it says or cap what it spends, that constraint is gone and the rollout decision moves back to you.
Where It Is in Context Memo
Open the Chat settings panel. The three new controls sit there alongside your existing Chat configuration: a guardrails field that governs chat behavior, a toggle for voice, and a daily budget limit. Changes you save in this panel apply to your Chat deployment, so one person on your team can set policy for everyone using it.
How to Use It
- Open the Chat settings panel. You will see the guardrails, voice, and daily budget controls on the same screen as your current Chat settings.
- Write your guardrails. State what Chat should and should not do: topics to stay inside, claims it must not make, how it should handle questions it cannot answer from your memos. Save, and the guardrails govern subsequent chat sessions.
- Decide on voice. Turn the toggle on if you want voice available in Chat; leave it off to keep Chat text-only. The setting takes effect for your deployment, not per user.
- Set your daily budget limit. Enter the ceiling you want for Chat spend in a single day. Chat spend stops at that figure, which gives finance a number to approve instead of an open-ended line item.
- Run a test conversation. Ask Chat something just outside your guardrails and confirm it declines or redirects the way you wrote it. Adjust the wording and re-test if the behavior is looser than you want.
- Record what you set and when. If your team has a review process for anything customer-facing, the guardrails text is the artifact to put in front of it.
Why We Built It
Customers told us they could not govern how their Chat feature behaved, could not control whether voice was enabled, and could not set spending limits. That meant Chat was either rolled out on trust or not rolled out at all. For teams with a legal or procurement review on anything buyer-facing, "not configurable" is the same answer as "not approved," and the cost was a feature sitting unused while buyers kept asking AI models about your category and getting answers from somewhere else.
What It Does Not Do Yet
These controls ship in the Chat settings UI. This deploy does not include a programmatic way to set them, so guardrails, voice, and the daily budget are configured in the panel rather than through an API or a bulk import. There is no alert tied to the budget threshold in this release either, so if you want to know how much headroom is left in a given day, check the setting.
Scope matters here too. Guardrails govern Chat behavior. They do not change how your memos are generated or what gets published to your domain, which remain separate controls in the memo workflow. If a model is describing your brand incorrectly in public answers, the fix is still a published memo, not a chat guardrail.