A team twin for the questions colleagues keep asking you

Answer your colleagues from internal material — without the twin ever deciding anything on your behalf.

What you will have at the end

A twin reachable only by colleagues you invite by email, answering from internal material, with no public page and no per-person trail.

Built from
Internal docs and notesProcess write-upsFiles you upload
What it produces
Answers from internal materialFewer repeat interruptions

Who it is for: Anyone who has become a bottleneck internally — founders, leads, and the person everyone DMs about how something works.

Overview

A team twin is you, answering invited colleagues from internal material. Invites are just email addresses, and access begins on first sign-in. It has no public page and appears in no listing.

The distinction that matters is authority. It reports what you have written down. It does not decide on your behalf, and it should not be set up as though it can.

Why this is a different twin rather than a setting on your public one

Internal material is the stuff you would never publish: half-decided positions, pay bands, the reason a project was cancelled. Keeping it in a separate twin with a separate audience is the only arrangement where a mistake in your public twin cannot leak it.

The failure mode of internal knowledge tools is staleness that nobody notices. Here the gap queue is the antidote — the questions colleagues ask that your material does not answer are a live list of what your internal documentation is missing.

Attribution is deliberately excluded. Team twins carry no per-person trail, because a tool that quietly records which colleague asked what is a surveillance product, and people stop asking honest questions the moment they suspect it is one.

Step by step

  1. Create it from the switcher

    Choose New team twin in the twin switcher. As with a support twin, it is a separate twin with its own knowledge and audience rather than a mode on your public one.

  2. Add the internal material — and only the internal material

    Upload or paste the documents colleagues keep asking you to explain: process write-ups, decisions and their reasons, the runbook that lives in your head.

    Be deliberate about what goes in. This twin should hold what you are willing for every invited colleague to read, and nothing beyond that.

  3. Invite people by email

    Invites are email addresses; access starts when someone first signs in. There is no public link to leak and no listing to be found in.

  4. Set the boundary between reporting and deciding

    Use scope boundaries to keep it on the material and off adjacent questions it has no business answering. The sentence to keep in mind is that it reports what you wrote, and never decides on your behalf.

    Test it in the private sandbox with the most tempting question — something where a colleague would love an answer and only you can actually give one. It should decline.

  5. Read the gaps as a documentation backlog

    The questions it could not answer are the internal documentation you have not written. Answer each once and the twin keeps that answer, which is a faster path to a written-down process than any wiki migration.

What this will not do

Every playbook carries this section, because a recipe that only lists what works is marketing.

  • It is not team accounts. Twins are owned by a person, not an organisation, and shared administration and company billing are still being built.
  • Invite-only access for any twin is not shipped — this is specific to team twins. Private mode on a public twin is an unlisted link, which keeps it out of search and listings but is not the same as gating it to named people.
  • There is deliberately no per-person attribution on team twins. If you need to know who asked what, this is not the tool.
  • It answers in Slack or WhatsApp only if you paste it there yourself. Multi-channel is something we are exploring, not something shipped.

Questions people ask first

Can a colleague share the link with someone outside the company?
There is no public link to share. Access is by email invitation and begins at first sign-in.
Will it show up in Google?
No. A team twin has no public page and is in no sitemap or listing.
Does it tell me which colleague asked what?
No, and that is deliberate. Lead and booking attribution explicitly excludes team twins — there is no per-person trail.
Is this the same as a support twin?
No. A support twin answers your customers from your product docs in a neutral product voice, reachable through a token your site mints. A team twin answers invited colleagues as you, from internal material.

Take it further

Build it free, and test the edge first

The Free plan includes a real published twin, and visitors always chat free. The private sandbox lets you break it before anyone else can — which is the step worth not skipping.

Start freeSee the live demo