Skip to main content

Sales with EnClaw — configure and use

A practical guide for the sales team, organised around the things you asked for. Each section shows how to configure it (a one-time setup) and how to use it (day to day). It's plain language — you work by chatting with an EnClaw assistant, the way you'd brief a capable colleague. It does the legwork; you stay in control and approve everything before it goes anywhere.

The things, in your words:

  1. I want to add a deal to HubSpot — originator, owner, due date, sales stage
  2. I want to know all the deals that are X weeks until they're due
  3. I want EnClaw to know all our case studies and the impacts we've made
  4. I want to create a case study at a moment's notice

How it works, in a nutshell

  • You ask in plain English — no forms.
  • It does the work — logs deals, pulls the pipeline, recalls and writes case studies.
  • You stay in charge — nothing is saved to HubSpot until you say yes.
  • It won't make things up — if it doesn't have an answer on file, it tells you.

You'll use two assistants: a Deal Desk Assistant for items 1 and 2, and a Case Studies Assistant for items 3 and 4. Set each up once, then just chat with it in its channel.

The setup basics (the same for both assistants)​

Creating an assistant is a one-time job — all menus and pasting, no coding.

Before the team starts — admin setup (one-time)​

A few connections must be in place first. Whoever has EnClaw and HubSpot admin access does these once; until they're done, an assistant will say it's "not connected".

  1. Connect HubSpot.
    • In HubSpot, go to Settings → Integrations → Private Apps → Create a private app. Give it access to deals (read & write) and owners (read), and copy the access token.
    • In EnClaw, go to Settings → Integrations → HubSpot, paste the token, and tick the allowed actions: deals read, deals write, owners read. Save.
  2. Add the originator field in HubSpot. Go to Settings → Properties → Deal properties → Create property, choose Single-line text, and name it originator. This is what lets a deal record who originated it. (Skip it and deals still log — they just won't carry the originator.)
  3. Connect SharePoint. In EnClaw → Settings → Integrations → SharePoint, connect your existing SharePoint/Teams connection and tick list read, list write, list bootstrap, and search read. Save.
  4. Check your branded deck skill is available. In the skills area, confirm your organisation's branded deck skill is imported/enabled — the Case Studies assistant uses it to produce on-brand documents.
  5. Put some case studies on file (only needed for "recall", item 3). Either seed the Case Studies list with your existing case studies (client, industry, services, challenge, solution, impact + a source link), or make sure your case-study files live in a SharePoint area the assistant can search. With nothing on file, recall honestly returns "nothing on file" — item 4 then builds the library over time.

To create an assistant​

  1. Go to the Agents area and choose Blank agent.
  2. Enter a Name.
  3. Choose the Model Provider and Model (use the recommended one; Fallback Model is optional).
  4. Copy that assistant's Identity to paste block (in its section below) into the Identity box — this is what tells the assistant how to behave.
  5. Under Agent Skills, switch on the skills listed for that assistant.
  6. Confirm Tool Preferences match that list.
  7. Click Save Changes.

To connect its channel​

In Slack, create the channel (+ → Create a channel) and invite EnClaw to it (/invite @EnClaw). Then open the assistant, go to Channel Bindings → Slack Channels, connect that channel, and send a test message.

You only configure each assistant once. After that, you just chat with it in its channel.

1. I want to add a deal to HubSpot

Configure it​

SettingValue
Assistant NameDeal Desk Assistant
Agent Skills to switch onHubSpot (CRM)
Channele.g. #sales-deal-desk
ScheduleNone — you ask when you need it
What its Identity doesLogs deals into HubSpot after you approve, and lists deals due soon — never guesses an owner or stage, never invents anything

Identity to paste (copy everything between the lines into the Identity box):

You are the Deal Desk Assistant for our sales team. You do two things: log new deals into HubSpot, and tell people which deals are due soon.

Logging a deal:
1. Make sure you have the deal name, who originated it, the owner, the due (close) date, and the sales stage. Amount is optional. Ask for anything missing before doing anything.
2. Match the owner and the sales stage to real values in HubSpot. If a name or stage doesn't match, show the valid options and ask — never guess.
3. Read the full deal back to the person and wait for their "yes". Only then create it in HubSpot.
4. After it's created, reply with a link to the deal.

Deals due soon:
5. When asked "which deals are due in the next N weeks?", list the open deals whose close date falls in that window, soonest first, with owner, stage and value. This only reads HubSpot — it never changes anything.

Rules you always follow:
- Never create or change a deal until the person approves the read-back.
- Never guess an owner or a stage — offer the real options instead.
- Never invent a deal, a date, or a number. If something's unknown, say so.
- Deals live in HubSpot only — never a spreadsheet or document.
- You never handle passwords or keys; HubSpot is connected by an admin.
- Use Australian English. Keep it brisk and sales-friendly.

Tone: a sharp, efficient sales coordinator — quick and clear, no waffle.

Identity sentinel: DEALDESK-AU-V1

One-time tip: for the originator to be saved, an admin adds a custom deal property called originator in HubSpot (Settings → Properties → Deal properties). Without it the deal still logs — it just won't carry the originator.

Use it​

  1. Open the Deal Desk Assistant's channel.

  2. Log a deal in one message:

    "Log a deal: Acme website rebuild, originator Priya, owner me, due end of August, stage Proposal."

  3. It works out who the owner is and which stage you mean, reads the whole thing back, and waits.

  4. Reply yes — it creates the deal in HubSpot and sends you the link.

Your part: check the read-back and say yes — nothing is saved until you do. Tip: plain dates are fine ("end of August"). If it can't match an owner or stage, it shows you the options to pick from.

2. I want to know which deals are due in the next few weeks

Uses the same Deal Desk Assistant as item 1 — no extra setup.

Use it​

  1. In the Deal Desk Assistant's channel, ask:

    "Which deals are due in the next 3 weeks?"

  2. You get a tidy list — due date, deal, owner, stage and value — soonest first, with a count ("7 deals due in the next 3 weeks").

Your part: nothing — just read and act on it. Tip: change the window to whatever you need ("next 2 weeks", "this month"). This only reads your pipeline; it never moves or changes a deal.

3. I want EnClaw to know all our case studies and the impact we've made

Configure it​

SettingValue
Assistant NameCase Studies Assistant
Agent Skills to switch onSharePoint list · SharePoint files · Branded deck
Channele.g. #sales-case-studies
ScheduleNone
What its Identity doesRecalls our case studies with proof, and drafts new ones on brand — always cites a source, never invents a result

Identity to paste (copy everything between the lines into the Identity box):

You are the Case Studies Assistant for our sales and marketing teams. You do two things: recall what our organisation has done for clients (with proof), and draft new case studies on brand.

Recalling our work:
1. When asked what impact we made for a client or in an industry, look only in our case-study records — the Case Studies list and our case-study files in SharePoint.
2. Answer with the client, what we did, and the measurable result, and include a link to where it came from.
3. If there's nothing on file, say so plainly and offer to create one. Never invent a client, a project, or a result.

Creating a case study:
4. Gather the client, the challenge, what we did, and the measurable impact (with a source). Ask for anything missing.
5. Produce a polished, on-brand case study — a slide deck by default, or a one-page document if asked — using the branded deck skill.
6. Save the case study to our records so the next person can find it.
7. If a number isn't confirmed yet, show it as [to confirm] — never make one up.

Rules you always follow:
- Recall only from real records, always with a source. "Not on file" is a fine answer.
- Never invent an impact figure; mark any unconfirmed number [to confirm].
- Everything on brand: use our organisation's typeface and colours.
- You never handle passwords or keys; SharePoint is connected by an admin.
- Use Australian English. Warm and concise.

Tone: a proud, precise storyteller who only deals in facts.

Identity sentinel: CASESTUDY-AU-V1

For recall to be useful, our case studies need to exist where the assistant can read them — either in the Case Studies list or as files in our SharePoint case-study area. If it's a fresh start, create a few with item 4 and the library builds itself.

Use it​

  1. Open the Case Studies Assistant's channel.

  2. Ask about a client or an industry:

    "What impact did we make for Acme?"

    "What have we done in retail?"

  3. You get a straight answer — the client, what we did, the result — with a link to the proof. If it's not on file, it says so and offers to write one.

Your part: nothing — just ask. Great for prepping a pitch or a "have we done this before?" check.

4. I want to create a case study at a moment's notice

Uses the same Case Studies Assistant as item 3 — no extra setup.

Use it​

  1. In the Case Studies Assistant's channel, ask for a draft:

    "Draft a case study for the Beta Bank project."

  2. It asks for anything it's missing — the challenge, what we did, the result — then produces a polished, on-brand case study and saves it to our records.

  3. Refine it if you like:

    "Make it a one-pager and lead with the cost saving."

Your part: give it what you have; it prompts for the rest. Tip: no hard number yet? It marks that spot [to confirm] rather than inventing one — drop the real figure in later. Once saved, item 3 will find it.

Go-live checklist

Tick these off, in order, before handing the assistants to the team:

  • HubSpot connected in EnClaw, with deals read, deals write, owners read ticked
  • originator deal property created in HubSpot
  • SharePoint connected (list read/write/bootstrap + search read)
  • Branded deck skill imported/enabled
  • Deal Desk Assistant created (Identity pasted, HubSpot skill on) and bound to its channel
  • Case Studies Assistant created (Identity pasted, SharePoint + branded deck skills on) and bound to its channel
  • Both Slack channels created, EnClaw invited, and a test message answered
  • Case studies on file (seeded list, or SharePoint files the assistant can search)
  • Smoke test passed: log a test deal · ask "deals due in the next 3 weeks" · recall a known client · draft a case study

When every box is ticked, the four scenarios all work end to end.

Good to know

  • You're always in control — nothing is saved to HubSpot, and no case study is finalised, without your say-so.
  • It won't make things up — no guessed owners or stages, and no invented impact figures; unknowns are shown as gaps or [to confirm].
  • Everything is on brand — case studies use your organisation's look and tone.
  • What it needs to be useful — HubSpot and SharePoint connected (your admin), and, for recall, your case studies on file.
  • If you get stuck, just ask the assistant in plain words — "how do I…?"