Chat responses seem generic or unhelpful
Chat responses seem generic or unhelpful
Be more specific. Add context about your company, role, and what you’re trying to accomplish. The more specific the question, the more specific the answer. See Prompting tips.Ask follow-ups. Chat keeps context within a conversation. “Can you elaborate on that?” or “What else should I know about this?” usually unlocks more depth than starting over.Check the citations. If an answer has few or no citations, GetWhys may not have enough research on your topic yet. File a Research Request — new interviews get added to your account in 10 business days at no additional cost.Try a template. The starter templates are tuned for common use cases and consistently produce better results than freeform questions. See Templates.
Message Testing feedback doesn't seem relevant
Message Testing feedback doesn't seem relevant
Check your persona setup. If your personas are thin or vague, the feedback will be too. Make sure each persona has filled-in challenges, motivations, KPIs, and job titles. Use the Test a persona template in Chat to validate.Check your brand voice setup. Same problem in reverse: short, vague characteristics with sparse do’s and don’ts produce sparse feedback. Specific, opinionated characteristics with concrete examples produce specific feedback.Make sure you picked the right persona. Easy to miss — confirm the persona selected at the top of the Message Test matches the actual target audience for the content.
I'm not getting the insights I need
I'm not getting the insights I need
File a Research Request. If GetWhys doesn’t have enough relevant interview data for your topic, our team will interview people who can answer your specific question. See Research Requests.Upload Organization Data. Combine your own win/loss interviews, sales calls, and research with the GetWhys research interview corpus. Often the gap is filled by data your team already has. See Organization Data.Refine your question. Ask a follow-up in the same conversation, or start fresh with a more specific prompt. See Prompting tips.
I can't access a feature I expect to have
I can't access a feature I expect to have
Features can be restricted by user type or by your organization’s settings. Check User types to confirm what your access level includes. If it should be available and isn’t, contact your organization admin or reach out via Teams, Slack, Google Chat, or email [email protected].
SSO sign-in fails or I don't see an SSO option
SSO sign-in fails or I don't see an SSO option
Confirm your work email domain is enrolled for SSO and that you’re assigned to the GetWhys app in your identity provider. See SSO setup. If SSO isn’t enabled for your org yet, or the ACS / Entity ID values may be wrong, reach out via Teams, Slack, Google Chat, or email [email protected].
My Gong calls aren't showing up
My Gong calls aren't showing up
Check that:
- The Gong integration is still connected on the Integrations page
- The Gong webhook is configured and active on the Gong side
- Your Gong automation rule filter actually includes the calls you expect
A document I uploaded isn't searchable yet
A document I uploaded isn't searchable yet
Processing happens in the background and usually finishes within a few minutes for typical documents. Larger files or large batches can take longer. The document appears in your Organization Data list immediately, but it won’t show up in Chat citations until processing finishes.If a document has been pending for more than 30 minutes, reach out via Teams, Slack, Google Chat, or email [email protected].
I forgot a feature exists or I want to suggest one
I forgot a feature exists or I want to suggest one
Reach out via Teams, Slack, Google Chat, or email [email protected]. Feature requests go straight to the product team.
Anything else
Anything else
Reach out via Teams, Slack, Google Chat, or email [email protected].