Search: Clarify the plan upgrade process when sites go over the Complete limits

[gibrown]

Impacted plugin

Jetpack

Quick summary

When a site goes over the 100k request/record limit that is in Complete they get emailed to upgrade by adding a Jetpack Search plan on top of their existing Complete plan. The existing UX, documentation, and support experience is confusing in a number of ways. See p1HpG7-v9n-p2#comment-74946

• https://jetpack.com/upgrade/search/ is not clear enough on what the pricing is (not sure the support docs are either)
• our internal tools don't help us to know what the user will be charged
• we should look for any other problems with the flow. Based on the stat in /s/jetpack-search-free-upgraded/jetpack-complete/ maybe something is also broken in the upgrade process?

Steps to reproduce

Not easy to reproduce, we need to hack the backend of a site to fake the number of requests. Maybe we want better tools for this.

A clear and concise description of what you expected to happen.

No response

What actually happened

No response

Impact

Some (< 50%)

Available workarounds?

No but the platform is still usable

If the above answer is "Yes...", outline the workaround.

No response

Platform (Simple and/or Atomic)

Simple, Atomic, Self-hosted

Logs or notes

No response

[github-actions]

Support References

This comment is automatically generated. Please do not edit it.

• p1HpG7-v9n-p2#comment-74946

[gibrown]

See also: https://github.com/Automattic/jpop-issues/issues/9373#issuecomment-2520290969

[supernovia]

@gibrown I'm working through our Needs Triage list for HEs. For now I'll change the status to Triaged, because the testing required isn't something HEs can do, and it's already in the correct repo. Feel free to change it back to Needs Triage if there's something we can help with!