Skip to content

Fix broken pricing link on pricing page#1093

Merged
bets-margulies-vapi merged 1 commit into
mainfrom
fix/pricing-broken-link
Jul 1, 2026
Merged

Fix broken pricing link on pricing page#1093
bets-margulies-vapi merged 1 commit into
mainfrom
fix/pricing-broken-link

Conversation

@claude

@claude claude Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Requested by Bets Margulies · Slack thread

Description

In the "Why is Vapi best in class?" FAQ answer, the visible "pricing page" link pointed to the wrong destination. This snippet renders on the FAQ page (docs.vapi.ai/faq, anchor #why-is-vapi-best-in-class) and the overview page — it does NOT render on the pricing page.

  • Before: The "pricing page" link in the "Why is Vapi best in class?" FAQ answer pointed to the internal docs /pricing route.
  • After: The link points to the marketing pricing page at https://vapi.ai/pricing.
  • Reported by priyanshu ranjan.

How

  • Updated the "pricing page" link on line 35 of fern/snippets/faq-snippet.mdx (inside the "Why is Vapi best in class?" accordion) so its href is https://vapi.ai/pricing. Visible link text is unchanged.

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work

Generated by Claude Code

The "Why is Vapi best in class?" FAQ accordion (rendered on the pricing
page via the faq snippet, anchor #why-is-vapi-best-in-class) linked to a
docs anchor instead of the pricing page. Point the "pricing page" link to
https://vapi.ai/pricing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SrAtybMEbiVnDqj8LjhoSJ
@bets-margulies-vapi bets-margulies-vapi marked this pull request as ready for review July 1, 2026 18:14
@bets-margulies-vapi bets-margulies-vapi merged commit 2c66caa into main Jul 1, 2026
6 checks passed
@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants