SayAll help
Clear answers for chat, accounts, and Credits.
Start with the topic you need. These answers describe the current SayAll text-chat product, including the details that matter when a free Credit, login, response, or payment does not behave as you expected.
Getting started
From the landing page to chat
Can I open SayAll without creating an account?
Yes. You can browse the public site, open the chat, create an empty conversation, and write a draft without registering. Merely viewing a page does not create a Guest record, Session, or Credit grant. SayAll waits until you actually send your first message before it attempts the Guest claim flow.
What happens when I send from a landing page?
The text you entered moves into the real chat in the current browser tab. SayAll does not put that prompt in the URL. This keeps it out of the address bar and referrer, and the temporary handoff is removed as soon as the chat reads it. After you enter the product, future visits to the root address can open the chat directly; use the public Home link when you want to return to the landing page.
Is SayAll currently text chat?
Yes. The current public product is browser-based text chat. SayAll does not advertise image or video generation on these pages. The browser sends ordinary user and assistant messages to SayAll, while provider routing and physical model details remain inside the service rather than appearing in the UI.
Accounts
Guest, email, and Google access
How does a Guest session work?
On the first send, SayAll uses browser/device and network risk signals to decide whether the one-time Guest trial is available. An eligible claim creates the Guest Session and 5 Credits together. The signals are lifetime de-duplicated; a different browser or changing network does not guarantee a second trial, and shared networks can make a trial unavailable.
How can I register or sign in?
You can use an email and password or Google. Email registration confirms a six-digit code before the account is created. An email password must be 8–32 Unicode characters, and paste and password managers are supported. Google accounts remain passwordless, so SayAll does not ask a Google-only account to create or change a password.
Will registration keep my Guest data?
Upgrading the current Guest through email registration keeps the same SayAll user identity, existing chat, and unspent Guest Credits. The registered daily grant can also apply that day. Google sign-in does not automatically merge the current Guest into a Google account, because an OAuth callback alone is not enough to expand the account-linking rules safely.
What if I forget an email password?
Start the password-reset flow with the account email. A reset code expires after 10 minutes, permits at most five incorrect attempts, and cannot be reused for registration. Completing a reset replaces the password, revokes older Sessions, and signs in with a new Session. Support should never need your password or verification code by email.
How many free Credits do I receive?
An eligible Guest can receive 5 one-time Credits on the first sent message. A registered user can receive 5 Credits per UTC day. Daily Credits expire at the next UTC midnight and do not accumulate. Before a Guest claim succeeds, the interface may describe the prospective allowance, but it cannot confirm a real balance that the Billing service has not created.
What costs a Credit?
The current text-generation rule is 1 Credit for one response. A service or upstream error refunds that charge in the same generation lifecycle. If you intentionally stop a response, the charge remains. SayAll uses Credits that expire sooner before durable Credits so a daily allowance is less likely to expire while an older purchased balance is spent.
Do purchased Credits expire?
Current one-time purchased Credits do not expire. The live Billing Catalog controls which packs are available, their currency, their price, and the number of Credits delivered. Check the Pricing page or the in-product Credits panel for the current Catalog rather than relying on an old screenshot or a third-party listing.
Responses
When a conversation stops or fails
Why can a response stop?
A response can complete normally, reach an output boundary, encounter a service or provider error, or be cancelled by you. Network interruptions do not automatically cancel a running generation; the chat reconnects through a current snapshot when possible. If an error ends the generation, its Credit is refunded. A user cancellation is final and is not refunded.
Why can a long message be rejected?
SayAll applies a bounded context policy before persistence, charging, and generation. A current user message that exceeds that input allowance is rejected before a Credit is spent. Shorten the message, remove repeated context, or split the work into several turns. A model’s willingness to discuss a topic does not remove technical context and output limits.
Does less restrictive mean every answer is guaranteed?
No. SayAll is built for broader lawful conversations, fiction, roleplay, and adult topics, but legal, safety, infrastructure, and service boundaries still apply. It also cannot guarantee factual accuracy. Verify high-stakes claims about medicine, law, finance, current events, or physical safety with reliable sources and qualified professionals.
Payments
Checkout and confirmation
Who can buy a Credit pack?
Credit-pack purchases require a registered SayAll account. The browser submits only the selected Offer code; the backend reads the amount, currency, and Credits from the active Catalog, then opens an allowlisted hosted checkout. This keeps a browser from replacing the commercial terms with its own values.
When will purchased Credits appear?
Credits are granted only after SayAll verifies a finished payment against the local Purchase. A success redirect is a status hint, not proof of payment. Pending or processing purchases can take longer to confirm. Repeated provider events reuse the same transaction identity, so they do not grant the same pack twice.
What if checkout remains pending?
Keep the local Purchase page available while confirmation is pending and avoid creating repeated checkouts for the same attempt. SayAll performs background reconciliation for recoverable states. Ambiguous payments, partial payments, or binding mismatches are held for manual review rather than granting Credits from an uncertain payment fact.
Human support
Still need help?
Email a short description of what happened and, when available, the request ID shown with the error. Do not include your password, verification code, Session token, payment credential, or private chat content.