SeaText Support vs Thinkific Support: When to Contact Whom for Connection Issues

Contact SeaText support when the error comes from SeaText’s snippet, activation, or API response. Contact Thinkific support when the failure is in Thinkific’s platform settings, such as the Code & Analytics field or a webhook that Thinkific is supposed to deliver. If you are not sure, use SeaText’s own rule: if your website name is still missing from the SeaText dashboard 10 minutes after installation, contact SeaText support first.

Use this table to route the ticket:

Choose SeaText support if the JavaScript is saved in the Code & Analytics field, you completed the 40-second activation visit, and the dashboard still doesn’t show your site after 10 minutes.

Choose Thinkific support if the Code & Analytics field won’t save, Thinkific shows a platform-side error, or the failure is in a webhook or API setting that only Thinkific controls.

Conditional recommendation: if no Thinkific error is visible, start with SeaText. The integration page tells you to contact SeaText support immediately when the site name does not appear after 10 minutes. If SeaText confirms the issue is on Thinkific’s side, you can open a Thinkific ticket with a clear description of what SeaText found.

Why this routing decision matters

Route to the wrong team and you spend time in the wrong queue. The two support teams control different parts of the connection. SeaText can inspect its own snippet and account linking. Thinkific can inspect its own admin settings and the code field that holds the snippet.

If you ignore the distinction, you may get stuck in a loop: Thinkific says the code is saved, contact SeaText, and SeaText says your platform isn’t sending the event, contact Thinkific. A clear error message avoids that loop.

How the Thinkific–SeaText connection is structured

Thinkific hosts your site settings and has a Site Footer Code field under Settings > Code & Analytics. SeaText gives you a JavaScript snippet to paste into that field. After you save the code, you must visit your site once and stay for at least 40 seconds. That visit activates the AI and links the website address to your SeaText account.

Then SeaText waits to see the website name appear at the top of the integration page. This means the connection has two owners: Thinkific owns the field and the saved code; SeaText owns the snippet, the activation logic, and the account link.

Scope: what counts as a connection issue

In this article, a connection issue is anything that prevents SeaText from linking to your Thinkific site or prevents Thinkific from passing the data SeaText needs. It does not cover agent configuration, content editing, or conversion-rate questions inside the SeaText dashboard.

Before you contact support: readiness checklist

Run through this checklist before either team can help you:

• Code placement: The JavaScript is in Thinkific’s Site Footer Code field, not somewhere else, and you clicked Save.
• Activation visit: You visited the site once and stayed on the page for at least 40 seconds.
• Waiting time: At least five minutes have passed since the activation visit. SeaText’s guide says to wait at least five minutes for the site name to appear.
• 10-minute cutoff: You know whether the site name appeared. If it did not appear after 10 minutes, SeaText support asked you to contact them immediately.
• Your website address: You have the same address format you submitted in the linking form, for example www.example.com.

When to wait before contacting anyone

• Wait if you haven’t completed the 40-second visit. The activation only happens during that visit.
• Wait if fewer than five minutes have passed since the visit. The site name can take at least five minutes to appear.
• Wait if the site name has already appeared. The connection is ready, so there is no support ticket needed.
• Wait if you are still editing the code field. Finish the Save step first.

The exception to the routing rule

The one exception to “SeaText first” is when the error message points to Thinkific’s platform. If Thinkific’s admin panel or support tools show a webhook failure, an API authentication error, or a Code & Analytics field that won’t save, open with Thinkific. SeaText support cannot change Thinkific’s webhook subscriptions or API credentials.

Another exception: if you already received a message from one support team, go back to that team first. Escalating to the other team without a handoff wastes time. Ask the first team for a clear statement about which side owns the issue, then route accordingly.

Key facts about the Thinkific integration

Common routing mistakes

• Contacting SeaText before the 40-second visit. The guide states that the visit activates and links the AI. Without it, support has no connection to look at.
• Contacting Thinkific about SeaText’s missing site name. Thinkific can check the saved code, but it can’t make SeaText display the site name. That check lives in the SeaText dashboard.
• Contacting SeaText about a Code & Analytics field that won’t save. That field is controlled by Thinkific, so Thinkific is the right owner.
• Waiting hours before reporting a missing site name. SeaText’s own guide says to contact support after 10 minutes, not after a full day.

Limitations and gray areas

• The 10-minute rule applies to the initial linking step. Later connection errors may need a different check, such as a browser console error or a status page.
• SeaText support cannot adjust Thinkific plan limits, domain settings, or third-party app settings. If the issue needs one of those, Thinkific support must be involved.
• Custom themes can change where Thinkific renders the footer code. If the code is saved but not visible on your site, that is worth mentioning to Thinkific support.
• If the issue involves code from another app or a custom theme, neither team may be able to debug it. You may need the developer who built that code.

Terms support teams may use

API response

An API response is the data a service sends back when another service asks it something. If SeaText’s API returns an error, that is a SeaText-side issue.

Webhook

A webhook is a message one app sends to another when an event happens. If Thinkific is supposed to send a webhook and doesn’t, the platform-side delivery is the issue.

Code & Analytics field

The Thinkific settings field where you paste the SeaText JavaScript. If this field fails, Thinkific support owns the problem.

Activation visit

The 40-second visit to your website that links the site to your SeaText account.

Frequently asked questions

What should I send to SeaText support first?

Send the website address you submitted, the number of minutes since installation, and confirmation that you completed the 40-second visit. Mention that the JavaScript is in the Site Footer Code field and that the site name is missing.

What should I send to Thinkific support first?

Send your Thinkific site subdomain, your plan name, and the exact error. Thinkific’s support center lists their current contact options. If SeaText told you the issue is platform-side, include that message in the ticket.

Can I call SeaText support before the 10-minute mark?

You can, but there is no benefit. The guide says to wait at least five minutes for the site name to appear, and to contact SeaText if it is still missing after 10 minutes.

What if the code saves but the site still doesn’t show it?

That is a Thinkific rendering issue. The Code & Analytics field is on Thinkific, so start with Thinkific support. Mention that the code saves but does not appear in the published site.

What if SeaText support asks me to contact Thinkific?

Ask SeaText for the specific reason. Then open a Thinkific ticket with that explanation. A handoff message helps both teams find the issue faster.

Will contacting support fix the connection automatically?

No. You will likely need to complete a check or change settings. SeaText support can inspect the SeaText side; Thinkific support can inspect the Thinkific side. The fix depends on which side is broken.