Foggetti Studio IT & StoreSoftware · AI · Automazioni
How to integrate ChatGPT into everyday business processes

Blog

AI & AutomationShort guide

How to integrate ChatGPT into everyday business processes

Clear guide to ChatGPT at work: allowed activities, rules, instructions and a two-week pilot.

7 minute read

Tuesday morning in a services SME. The salesperson just finished a site visit and needs to send the follow-up. They open ChatGPT on a personal phone, paste the notes as written — names, addresses, a few figures — and ask for «a professional email». In two minutes they have a decent draft. Nobody in the company knows that text left through a private account, or which data ended up in the chat.

It happens more often than people admit. Not because staff are reckless on purpose: because the tool is useful and nobody has said where yes and where no. The message, without spinning: ChatGPT can save time, but employees must not use it freely with confidential data. The company must decide which activities to use it for, provide ready-made instructions, have a person check the results, and verify that time savings are real.

Why DIY does not hold for long

When everyone sets their own rules, three problems arrive together. First: you no longer know which activities the team already uses the model for. Second: without shared instructions, the same customer gets different tone and detail depending on who writes. Third: price lists, margins, staff data or entire contracts land in non-company chats, with no useful trail.

In practice the company gains scattered hours and loses control. That is not an argument against AI. It is an argument against improvisation. A small test, with a clear owner and human review before send, beats twenty personal accounts left free.

Start from activities, not from the tool

The solid way to introduce ChatGPT is simple and often skipped: list the repetitive tasks that waste time. Follow-up emails after a visit. Meeting summaries. Pre-job checklists. First read of a support request. For each one write, in plain language, what goes in, what must come out, who re-reads it and what happens if the result is wrong.

Approve only low-risk activities. Internal drafts and summaries are fine. Negotiated prices, contractual commitments and decisions that bind the company stay out — or must pass an expert. Three to five allowed activities (and a clear forbidden list) beat any generic AI course.

One-page rules, not a fifty-page policy

You need a rule people will actually read. One page is enough. Write what must not be pasted: unnecessary personal data, customer codes, confidential attachments, non-public price lists. Write what is allowed: anonymised text, generic drafts, rephrasing. Name official company accounts and end the season of personal logins on work PCs.

Add one line on accountability: if a message goes to the customer, a named person checked it. That is not bureaucracy. It is the simplest way to stop «ChatGPT said so» becoming an excuse when something goes wrong.

Ready-made instructions (the prompt library)

Without shared instructions, every colleague reinvents the world. Prepare eight to twelve ready prompts in a sheet or Notion. Each card says what to obtain, which minimum inputs to give, the limits («professional tone, max 120 words»), the output format and a good example next to a bad one.

Keep them current. A prompt that works today and is written nowhere becomes personal knowledge within a week. Name an owner, mark the current version and spend thirty minutes a week fixing three real cases. That beats an eight-hour course done once.

A two-week trial that tells the truth

Pick one flow — for example the post-visit email draft — and three to five people. They use only approved instructions. Every text going to the customer passes a person. Log times, corrections and moments when the model invents details nobody put in the notes.

If time really drops and errors stay few, add a second activity. If corrections are too many, improve instructions and inputs — do not buy another tool. Note what must stay manual. Only when instructions are stable does it make sense to connect drafts to email or CRM notes — and in month one, no automatic send to the customer.

An example that comes up often

A services SME with about a dozen people was losing six to eight hours a week on follow-ups and visit summaries. They limited ChatGPT to three activities: follow-up draft, note summary, pre-job checklist. Clear rule: no full price lists or complete customer records in prompts. Ten library instructions, mandatory check by the owner or senior salesperson. After three weeks writing time was down about a third, with zero wrong sends — precisely because a person always re-read before send.

In short: the operating framework

Short version to print or paste into a meeting.

Steps

  1. Choose 3–5 repetitive activities + a forbidden list (day 1–2).
  2. Write 1-page rules: forbidden/allowed data, accounts, who checks.
  3. Prepare 8–12 ready instructions (goal, limits, example).
  4. Trial 2 weeks on one flow, 3–5 people, mandatory human check.
  5. Measure, fix instructions/inputs, expand only if savings are real.

Quick checklist

  • Allowed and forbidden activities communicated to the team.
  • Company accounts active (no personal logins at work).
  • Instruction owner named.
  • A person checks every outbound customer text.
  • Week-zero times logged (for comparison).

KPIs (max three)

  • Average time to write a draft (minutes, before/after).
  • How often a person corrects the output.
  • Data incidents (prompts with forbidden info): target zero.

Practical value (and the next step)

To recap: ChatGPT can save time, but employees must not use it freely with confidential data. The company must decide which activities to use it for, provide ready-made instructions, have a person check the results, and verify that time savings are real. Practical value is not «having AI»: it is fewer hours on repetitive drafts, fewer mistakes toward the customer, and less risk of sensitive data leaving through a personal account.

This week, in half an hour: write three to five allowed activities and what is forbidden, name who checks outbound messages, and pick one flow to trial for two weeks. Bring the schema to the meeting and treat it as an operating checklist.

If you want to set rules, instructions and a pilot on your real workflow, Foggetti Studio can help starting from your team's actual process.

How to integrate ChatGPT into everyday business processes | Foggetti Studio