Why TeleportHQ?

TeleportHQ for agencies: deliver sites your clients can run themselves

TeleportHQ for agencies: deliver sites your clients can run themselves

In TeleportHQ, an agency designs and publishes a client's site in the editor, and the client runs the live site from the admin panel on their own site: orders, products, bookings, blog posts, users, files and new pages built from blocks, without opening the editor. You keep every client in one agency workspace with a folder per client, or build in a workspace the client owns. The Growth coach watches each site and emails you, not the client, what needs a look. This guide says what you get on day one, what the first week looks like and what you will be asked to decide before you build.

Who this guide is for

  • Agencies, freelancers and studios building sites for several clients.
  • Anyone delivering a website, a store or a booking site that the client must update themselves afterwards.

What you get on day one

What stays with the agency, in the editor: the design, the layout and the texts of the pages you designed, the workflows, the project settings and publishing.

What happens in the first week

  • The client works in the admin panel; you hear from the coach. Each project's Growth coach reads the site's visitors once a day and lists what to change under Growth → Today in that project. Its emails go to the workspace owner by default, to members who can edit the project only if they switch on Alerts by email, and never to Viewers or Limited Viewers. So in an agency workspace, you get the daily digest (about 8 in the morning, on days with news) and the critical alerts, and a client invited as a Viewer gets none. In the client's own workspace, the client, as owner, gets them unless they switch them off. See How to set up Growth Settings.
  • "Your site is not answering" reaches you first. TeleportHQ checks each published site every 15 minutes; after three misses in a row (about 45 minutes) the email goes out at once, and so does "Your site is back" when it answers again. Weekly, each site gets its audit again, a link check and a Search Console read. See How to keep an eye on your site every week (SEO Monitoring).
  • Each project's numbers live in that project. Visitor analytics, the site health audit, form submissions, orders and bookings are under Growth in that project's editor; there is no cross-client dashboard. See How to see who visits your site (Analytics).
  • Automations do the follow-ups. For a client's store, Growth → Automations sends a thank-you when an order is paid or a note when stock runs low; the client sees the results, you edit the steps. See How to send emails automatically when something happens on your site (Automations).
  • The Monday report can go to the client. With AI coach and Weekly report on, the report is emailed to everyone whose Alerts by email is on, in the site's language. It uses the workspace's AI tokens (at least 600 per report).

What you will be asked to decide

  • Where the site lives, before you build it. There is no "move this project to another workspace" command, and a workspace's ownership can't be transferred. Either build in the client's own workspace from the start, with you as a member, or keep it in your workspace with the client as an admin on their site and a free Viewer or Limited Viewer in the workspace. A Can clone link gives the client a copy, not a move: the copy starts unpublished, without the domain, the Secrets, the payment set-ups or the customer data. See Can I transfer a project to another account?.
  • Who pays for what. AI tokens are a workspace balance shared by all its projects and members; editor seats are per workspace, with Viewers and Limited Viewers free; custom domains come in slots per workspace; each web app needs a Web App slot after its first 7 days. See What are AI tokens, and how many do I get?, How do editor seats work?, How many custom domains can I connect? and Why does my web app need a slot?.
  • Which emails reach the client. The coach's emails follow the roles above. The emails the site sends to the client's customers (orders, bookings, newsletters) go through an email provider connected in the client's project, on an account the client or you own. See How to choose which email and SMS provider your project sends through.
  • Which plugins the client runs. A store, bookings, a blog, a help center and a newsletter each add their own screens to the admin panel; the client never needs the editor for them. The design of their pages stays yours.

Where to start

  1. What is a workspace? and What can each role do?
  2. How to duplicate a project (and reuse it like a template)
  3. How to add sign-up and login to your site, then How to turn on the admin panel
  4. How to set up Growth Settings: who gets the coach's emails

Every new TeleportHQ account starts with a free 7-day trial, with no credit card, on 1 project. See How does the TeleportHQ free trial work?.

Share

Related Articles

Why TeleportHQ? Is it right for your project?

TeleportHQ builds a website or web app from a description of your business, runs it (eleven plugins, from a store and bookings to a newsletter and an age gate, each one switch whose pages, data, emails and admin screens come wired) and watches it for you (a Growth coach reads your visitors once a day, emails you a daily digest and a Monday report, and hands the fixes to the AI Assistant); this guide says who it suits, where a coding assistant or another builder is the better choice, and how it compares by kind of tool.

What is a workspace?

A TeleportHQ workspace is a shared space with one Owner that holds projects, members with roles, and its own plan and billing; you can own several workspaces and be a member of other people's, all listed in the dashboard sidebar under WORKSPACES and SHARED WITH ME.

What can each role do? (Admin, Designer, Editor, Viewer)

TeleportHQ has six roles (Owner, Admin, Designer, Editor, Viewer and Limited Viewer); Owner, Admin, Designer and Editor can edit and use an editor seat, Viewers are free and read-only, and the Editor role can't publish, view code, edit components or see every page by default.

What is the admin panel?

The TeleportHQ admin panel is a back office that TeleportHQ builds for your web app at /admin/dashboard on your published site, where people with the admin role manage users, orders, products, bookings, invoices, blog posts and comments, files, sent emails and your own database tables, and build extra pages from blocks, without opening the editor.

Can I transfer a project to another account?

No, TeleportHQ can't transfer project ownership or move a project to another workspace, but you can give someone their own copy by setting the project to Can clone and sending the link, or give them access by inviting them as a collaborator.

How to set up Growth Settings (AI coach, weekly report, email alerts and social proof badges)

In TeleportHQ, click the Growth Settings gear at the top of the Growth panel to turn on the AI coach and the Monday weekly report, choose whether you get Growth alerts by email, and show or hide social proof badges such as 12 bought this week on your store and booking pages.