fix: registration must state the account code back to the customer#36
Merged
Conversation
The account-registration skill listed reading back the accountCode as a soft step, and the model skipped it ~half the time — leaving a chat-registered customer with no way to learn the code they need to set up web login. Make it a hard requirement: the confirmation reply MUST state the code verbatim, with an example, and never finish registration without it. Verified live 4/4 registrations now state the code. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A chat-registered customer needs their
accountCodeto set up a web login (the cross-channel bridge from #35). Theaccount-registrationskill suggested reading it back, but the model skipped it roughly half the time — leaving the customer with no way to get the code (they can't reach/accountwithout first logging in). That's a broken customer workflow, not just flakiness.Fix
Make stating the code a hard requirement in the skill: the success reply MUST include the code verbatim, with a concrete example format, and must never finish registration without it.
Verification
Live, via the real agent through the gateway: 4/4 completed registrations now state the code in the confirmation (1 single-turn + 3 two-turn confirm flows). Data plumbing was already correct (the register tool returns the code); this closes the model-behavior gap.
🤖 Generated with Claude Code