Build with Emma: build from a prompt
Build a workflow from a prompt with Build with Emma.
Read the lesson
Goal: Write a clear prompt for Build with Emma. Review every step it drafts. Publish only what you have checked.
You need: Lessons 1, 2 and 5 of this course. Core, Growth or Franchise.
Why this matters
Build with Emma turns a plain description into a draft workflow. A good prompt saves you 15 to 30 minutes per workflow. Across 10 clients, that adds up fast. But Emma builds what you describe, not what you meant. A vague prompt gives a draft with missing conditions, wrong timing or the wrong trigger. Your skill is the prompt and the review. Emma does the clicking.
How Build with Emma works
Open Workflows and click Build with Emma. The flow has 4 steps.
- Describe: you write the outcome in plain words.
- Review: Emma shows the draft workflow. You read every step.
- Test: you run the builder
Test, which sends nothing. - Activate: you publish when it is right.
The four steps of Build with Emma
- 1DescribePaste the 7-part prompt
- 2ReviewCheck every step Emma drafts
- 3TestA free simulation, sends nothing
- 4ActivatePublish when it is right
The draft is a draft. Nothing sends until you publish. You can still edit any step in the builder after Emma drafts it.
Build with Emma is not listed on the Credit Calculator. Check Billing → Usage history after your first use. The workflow it builds costs the same as a hand-built one. Plan 1 credit a run plus what it sends.
The 7-part prompt
Write every prompt with these 7 parts. Short sentences work best.
- Trigger: "When a new deal is created in the Proposal stage."
- Who: "Only customers, not staff or test contacts."
- Steps: "Text on day 1. Email on day 3. Text on day 7."
- Checks: "Before each message, check the deal is still in Proposal."
- Words: "Use this text: ..." Give the exact message, or ask for a draft you will edit.
- Owner: "If no reply by day 7, create a task for Dev."
- Limits: "Keep texts under 160 characters. No emoji."
Brightline's 7-part prompt
| Part | What Brightline's prompt says |
|---|---|
| 1. Trigger | A new deal is created in the Proposal stage |
| 2. Who | Only customers, not staff or test contacts |
| 3. Steps | Text day 1, email day 3, text day 7 |
| 4. Checks | Before each message, the deal is still in Proposal |
| 5. Words | The exact approved text for each message |
| 6. Owner | No reply by day 7: a task for Dev |
| 7. Limits | Texts under 160 characters, no emoji |
Use the account's exact names for stages, tags and fields. If the pipeline stage is Proposal, write Proposal, not Estimate. The checks in part 4 matter most. The builder has no stop rule. Without a check before each message, a customer who already said yes still gets the day 7 text.
Review every step
Read the draft from top to bottom. Ask these questions.
- Is the trigger the one you asked for? Watch for Deal Updated instead of Deal Created. Deal Updated fires on every edit and can start the sequence again.
- Do stage, tag and field names match the account exactly?
- Is there a
Conditionbefore each message? - Are the delays the right length?
- Is the message text exactly what you approved?
- Does every path end in an action?
- Does the task go to a named person, with a due date?
Fix anything wrong in the builder. Then run Test with 3 sample contacts.
When to build by hand instead
Build with Emma is fastest for simple, common flows: a reminder, a thank-you, a quote follow-up. For a workflow with 3 branches and an AI step, building by hand is often faster. You would spend longer fixing the draft than placing the steps yourself. A good rule: if your prompt needs more than 10 sentences, build by hand.
Template, Emma or by hand?
- A client needs a new workflow
- Does a template fit?YesStart from the template. Change the words and timingNoGo to the next question
- Does the prompt need more than 10 sentences?YesBuild it by handNoUse Build with Emma
- Review, Test, gated live test, Publish
Start from a template when one fits. Templates include Appointment Reminder, New Lead Follow-up and Post-Service Survey. A template is already tested by ServiceAgent. You only change the words and timing.
By business size
An owner-operator needs 3 to 5 simple workflows. Build with Emma or a template covers all of them. A fleet needs more branches and more checks. Use Emma for the draft, then expect real edits. For a multi-location client, build once in the first location. Rebuild in each other location from your saved prompt, and check Working in each time.
Build it in ServiceAgent
- Write the 7-part prompt in a text file first. Keep it. You will reuse it for other clients.
- Open
Workflows→Build with Emma. Paste the prompt. - Review the draft against your 7 parts. Fix each gap in the builder.
- Click
Testwith 3 samples: a new quote, a quote already won, and a staff contact. - Add a test gate and publish. Run one live test on your own contact (lesson 5).
- Remove the gate. Publish again.
- Check the client's active count. On Core, this workflow counts as 1 of 10.
- Check it works: read
View run historydaily for the first week.
Worked example: Brightline Electric
Brightline Electric has 3 people on Core. Owner Dev sends about 25 quotes a month. Many go quiet. You write the 7-part prompt above and paste it into Build with Emma.
Emma's draft had two problems. It used Deal Updated as the trigger. Every edit to a deal would have restarted the texts. It had no check before the day 7 text. A customer who said yes on day 2 would still get it. You changed the trigger to Deal Created with a Condition for the Proposal stage. You added a Condition before each message.
Emma's draft for Brightline, before and after review
- Trigger: Deal Updated
- Every deal edit restarts the texts
- No check before the day 7 text
- A day 2 yes still gets the day 7 text
- Trigger: Deal Created
- Condition: stage is Proposal
- A Condition before each message
- A yes stops the later messages
Credits, worst case: each quote gets 1 run, 2 texts and 1 email. That is 1 + 2 + 2 + 0.5 = 5.5 credits a quote. 25 × 5.5 = 137.5 credits a month. Quotes that close early skip later messages, so the real number is lower.
Brightline worst-case credits
You could also start from the Estimate Follow-Up Sales Sequence template. Compare both and keep the simpler one.
Common mistakes
- Mistake: Publishing Emma's draft without review. Fix: Check every step against your 7 parts.
- Mistake: A vague prompt such as "follow up on quotes." Fix: Use the 7-part prompt.
- Mistake: Missing checks before each message. Fix: Ask for them in the prompt, then confirm them in the draft.
- Mistake: Not saving the prompt. Fix: Keep it. It is the start of your next Blueprint.
Do this now
Write a 7-part prompt for one workflow your clients need. Run it through Build with Emma in your practice account. List every change you made to the draft. Deliverable: the prompt and a change list. Time: 25 minutes.
Practice the conversation
- Owner Can the AI just build my follow-ups?
- Operator It drafts them. I check every step before anything goes live.
- Owner Why check?
- Operator The first draft for you would have texted customers who already said yes.
- Owner That would look bad.
- Operator Right. I added a check before each message.
- Owner How many quotes will it chase?
- Operator All of them, about 25 a month for you.
- Owner And it stops when they book?
- Operator Yes. Each message checks first.
Quick check
- Emma's draft uses Deal Updated as the trigger for a quote follow-up. What is the risk?
- It never fires.
- It fires on every edit and can restart the sequence.
- It costs 5 credits a run.
- It only works on Franchise.
- A sequence sends 2 texts and 1 email per quote. Each run is 1 credit. How many credits for 40 quotes, worst case?
- 160
- 200
- 220
- 240
- Which prompt part stops a customer who already booked from getting more messages?
- Trigger
- Words
- Checks before each message
- Limits
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.