Policies
Policies hold your business rules in one place: your refund window, who can pay cash on delivery, when a case goes to a person, and why. Each policy links to the flows, settings, FAQs and data points that carry the rule out. When any of them changes, Flowcall checks the policy again and flags it if the two no longer agree.
Your flows still decide what happens in a conversation. A policy records the rule and the reason for it. Copilot uses that to keep your configuration consistent, and, if you turn it on, the AI uses it to explain rules to customers.
Policies are in the Policies tab of the Copilot workspace (see Copilot layout). You write and change them by asking Copilot; the tab shows each policy's status and the actions that need no editing. Saving or changing a policy needs the Configurations permission.
Getting started
An account starts with no policies, and nothing uses them until you add some. To create the first set, open the Policies tab and choose Generate policies. Flowcall reads all your live flows, settings and FAQ answers and proposes one policy for each rule area they carry out, such as refunds, cancellations, COD or product issues. Where a rule differs by product type, the policy states each product type's rules. Generating can take a few minutes. Nothing is saved yet: untick the ones you don't want and choose Save.
Copilot doesn't write an account's first policies. Once your account has policies, Copilot adds and updates them as you change your configuration: choose New policy or Ask Copilot on a policy to start the message in the chat, finish it, and send it.
What a policy contains
Each policy covers one rule area, such as refunds, COD or escalation:
- Title and Summary: a name and a one-line description of what the rule is about.
- Key: a short, stable name such as
refunds. Copilot and the policy history refer to the policy by it. It's filled in from the title when you leave it empty. - Customer text: the rule as a customer may be told it. This is the only part the AI can use in customer replies.
- Internal notes: why the rule exists, internal exceptions, fraud thresholds, and when agents may use their judgment. Never shown to customers.
- Links: the flows, settings, FAQs and data points that carry out the rule.
- Intent only: for a rule that no configuration carries out yet. An intent-only policy has no links, so it is never checked and never used in replies.
A policy states the rule and why. Leave out how a flow is built, such as the questions it asks or the order of its steps. That belongs in the flow itself.
References in policy text
A reference in a policy shows the current name of a flow, FAQ or data point, or the current value of a setting. If you write "COD is available up to ₹" followed by a reference to your maximum COD order value setting, the policy always shows the value that is actually set. Change the setting and the policy text follows.
Copilot writes references for you, and every reference also becomes a link. A flow name in the text is turned into a reference when the policy is saved, and Copilot uses a reference rather than typing a setting's current value, because a typed number goes out of date when the setting changes.
Policy statuses
Each policy in the Policies tab shows its status:
- Current: the policy matches its linked configuration.
- Being checked: something it links to changed, and the check is running.
- Needs review: the check found a conflict, or a linked item was deleted.
- Draft: written but not approved. Drafts are not checked and not used anywhere.
- Waiting for publish: Copilot wrote the policy along with flow changes that aren't published yet. See Changes that wait for a flow.
- Archived: no longer used. Turn on Show archived to see archived policies and restore one.
How policies stay in step with your configuration
Flowcall checks a policy again whenever something it links to changes:
- a linked flow is published (unpublished drafts don't count);
- a linked setting is saved;
- an FAQ is added, edited or re-uploaded;
- a linked data point is changed.
The check runs within a few minutes of the change and compares what the policy says with what the configuration now does. When they still agree, the policy returns to Current without anyone having to do anything. When they conflict, the policy becomes Needs review. The Policies tab then shows what changed and the conflict in plain words, for example "the policy says refunds within 7 days, but the Refund request flow now accepts 10".
Every policy is also checked once a night, which catches changes made in other ways. Check now at the top of the tab runs the check right away.
Dev and prod
A flow can be turned off in dev (your test environment) or in prod (real customers). A linked flow that isn't on in both shows where it runs, for example dev only. Turning a flow on or off in either environment counts as a change, so its policies are checked again. A policy that relies on a flow that is on in dev only, or turned off, is flagged: real customers aren't served by that flow, so the rule isn't actually carried out for them.
Changes that wait for a flow
Copilot's flow changes are drafts until you publish them. When Copilot changes a policy together with a flow, for example after you say "refunds are now 10 days", saving the Policies card doesn't make the policy change live straight away. It waits until the flow is published, so the policy never tells customers a rule the live flow doesn't follow yet.
While it waits, the policy shows the waiting change and the flow it's waiting for:
- Publish the flow: the change goes live within a few minutes and is checked against what you published.
- Discard the flow's draft: the waiting change is dropped. A new policy that was waiting is removed.
- Apply now: makes the change live without waiting.
- Discard: drops the waiting change and keeps the policy as it is.
The policy that was live before keeps being used until the change goes live. A later change to the policy replaces a waiting change.
Reviewing a flagged policy
A policy marked Needs review can be resolved in three ways:
- The configuration is wrong: fix the flow, setting or FAQ. The next check returns the policy to Current.
- The policy is out of date: choose Ask Copilot to resolve, or tell Copilot what the rule is now, and save the Policies card it proposes. Saving confirms the policy against your configuration as it is now.
- Both are fine: choose Still holds, mark as reviewed. This confirms the policy without changing its text.
If a linked item was deleted, ask Copilot to remove or replace the link before you mark the policy as reviewed.
To take back a change Copilot saved, use Undo on its Policies card. Archive stops using a policy; turn on Show archived and choose Restore to bring it back.
Using policies in customer replies
The Use in customer replies panel controls whether the AI uses policies when it talks to customers. All three uses are off until they are turned on:
- FAQ answers: when an FAQ linked to a policy answers a customer's question, the AI also sees the policy.
- Completion messages: when a flow finishes, the policies linked to that flow help its closing message state next steps and timelines accurately.
- Task replies: while a flow runs, the policies linked to it are available on every reply, so the AI can explain a rule when the customer asks why.
Only the customer text of Current policies is used, and only through the flows and FAQs a policy links to. Internal notes never reach customers. The AI is told that policies explain rules and that the flow decides what happens, so it should not promise a refund or a handoff that the flow hasn't made. Flows set to send a fixed completion message don't add policies to it.
While policies are being piloted, Flowcall turns these switches on for your account.
Policies and Copilot
Once your account has policies, Copilot sees the list of your policies and can read any of them. You can ask it to write a policy, update one, archive one, or confirm one that was flagged. It shows the change as a Policies card for you to save, and you can undo a saved change from the card.
Copilot also checks policies when it changes your configuration. Before it edits a flow, setting, FAQ or data point that a policy links to, it reads the policy and tells you if the change would contradict it. When you state a new rule, such as "refunds are now 10 days", it plans changes to both the policy and the configuration that carries the rule out. The policy change waits for the flow to be published, as described in Changes that wait for a flow.
In an account without policies, Copilot doesn't create them. Ask it about policies and it points you to Generate policies in the Policies tab.