Quickstart: ZUZU

ZUZU is the assistant your Stackado apps are operated through. You give it one outcome in plain language. It plans the steps, hands each step to the app that owns that kind of work, and stops for you before anything goes live.

Before you start

1. A plan that includes ZUZU. Your plan also sets how many credits are included each month, and every run spends from that balance.
2. At least one connected app or account. ZUZU can research and draft without one, but it cannot read your mail, your customers, or your site until something is connected.
3. Your business context. What onboarding captured about your business is what keeps drafts sounding like you instead of like a generic template.

Your first ten minutes

You do not have to know what any of the apps are called. Everything below happens in one conversation, one question at a time, and you can skip any of it.

1. Sign up and answer the short setup. Give your website address if you have one — ZUZU reads it in the background and fills in your business details while you carry on. If you do not have a site, you can type the details instead. The intro video can be skipped and never blocks you.
2. Open ZUZU. Tell it what you want to work on, or ask it to help you finish setting up your workspace.
3. Ask “Help me set up Zuzu”. It asks two questions — what you are mainly trying to do, and which parts of the business you care about right now — and then walks you through the rest one step at a time.
4. Confirm what it knows about you. One line to check, not a form. If it has no logo or product photos, it offers to take them here.
5. Pick the two or three apps that fit. For each one, ZUZU asks for the thing that app would give you, tries it, and shows a button to connect whatever is missing. Pressing that button opens the real connection screen and brings you back to what you were doing.
6. Try one thing. ZUZU offers only work your workspace can actually run right now, so nothing you press can fail for a missing setup.
7. Say yes to the morning brief. It arrives at a set time in your own timezone, and ZUZU tells you exactly when it armed it. Say no and nothing is created.
8. Let it learn how you write. Optional, and offered again whenever you want it.

At the end you get a short summary of what is ready, what you skipped, and one thing worth doing next. Finishing the walkthrough is not the same as being finished: it means the conversation is done, and anything you skipped is still waiting whenever you want it. You can ask to set up ZUZU again at any time.

What ZUZU can do right now

The honest answer depends on your workspace, so ask it rather than reading a list that may not apply to you. In the chat, ask “what can you do?” — or name an app, as in “what can you do with my mail?” — and it answers from what is actually connected, switched on and included in your plan, saying which things still need setting up.

Everything it lists follows the same rule: reading, researching and drafting happen on their own, and anything that sends, spends, books or changes a setting waits for you.

Stackado is in beta and this list grows. The changelog records the latest changes.

Your first run

This example uses Zendo - Mail, because a mailbox is the fastest connection to make and the easiest result to check.

1. Connect a mailbox from the Integrations screen, or from the setup card ZUZU shows you in the chat itself.
2. Open ZUZU and describe the outcome, not the steps. For example, “Turn this offer into a campaign draft and stop before anything sends.”
3. Read the plan it comes back with. Each step names the app that will do it.
4. Let it run. Steps that only read or draft go ahead on their own.
5. Review the draft in Zendo, then approve the send when you are happy with it.

What waits for your approval

ZUZU researches, reads, and drafts on its own. It stops and asks before anything that leaves your account or cannot be taken back:

• Sending, publishing, or posting anything to a customer or an audience.
• Spending money, and booking anything on a calendar.
• Applying settings to a connected app.
• Deleting anything you did not explicitly ask to delete.

Approval is per action, and the riskier half of a plan never inherits the approval you gave the safer half. Everything a run did stays readable afterwards, so you can check what happened rather than take its word for it.

When a run stops early

• Something is not connected yet. ZUZU says which account it needs and offers to connect it there in the chat. Connect it and ask again; it keeps the context.
• Not enough credits for the next operation. It does not start unless Stackado can reserve its estimated cost. Completed steps stay in the run. Top up or wait for your monthly allowance to reset, then retry the blocked step.
• A step failed. The plan tells you which step and why in plain language. Fix the cause and use Retry on that step. Completed steps are left alone.