Repository navigation
Document traffic splitting stickiness and the repeat caller opt-out - #1307
Draft
peter-vapi wants to merge 2 commits into
Draft
peter-vapi wants to merge 2 commits into
peter-vapi wants to merge 2 commits into
Conversation
Replace the "sticky routing is best effort" framing with the actual deterministic mechanism: caller identity hashes to one of 100,000 buckets, targets own contiguous ranges in listed order, and nothing is ever stored. This explains why ramping only moves callers forward and why reordering targets re-deals ranges. - Add a worked bucket-range table showing a 90/10 to 50/50 to 100% ramp and which callers move at each step - Add an identity-class table (phone, SIP, web, withheld, saved customer id) with per-situation stickiness behavior and examples - Document the new repeatCallerStickiness: false opt-out, including its default (true), its rejection when combined with allocationIntent: follow-latest, and an API example - Add guidance for testing both arms of a split from one's own phone by disabling stickiness temporarily Fixes DEPLOY-172 Must not merge before the repeatCallerStickiness API change deploys. OpenCode session ID: ses_f108c3e24ffe0wHXs7DTqREQtW
- Add dashboard steps for clearing the "Repeat caller stickiness" checkbox in the traffic editor, reachable from the traffic pill or the Traffic step when publishing - Note that the dashboard persists the setting across future splits - Keep the existing API opt-out instructions (repeatCallerStickiness: false) as the alternative path, now clearly separated from the dashboard flow Fixes DEPLOY-176 OpenCode session ID: ses_f108c3e24ffe0wHXs7DTqREQtW
Contributor
|
🌿 Preview your docs: https://vapi-preview-01a12275-4d1d-7680-8600-3510e7a4f5d2.docs.buildwithfern.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.
Description
repeatCallerStickiness: false. It defaults totrue, and sending it withallocationIntent: "follow-latest"is rejected.Testing Steps
fern docs devor navigate to preview deployment#how-stickiness-worksresolves (the dashboard's "Learn more" link targets it)