Skip to content
Let’s talk
Insights · 18 November 2026

Agentforce Coworker: what to check before a pilot.

Salesforce’s November announcement is a reason to review where AI could help your team. Start with a defined task and evidence of a useful result.

Salesforce cloud and Agentforce character beside green glass panels in a sunlit architectural courtyard
Start with one workflow, clear permissions and human review. Adaptal concept illustration.

What has changed?

On 4 November 2026, Salesforce announced expanded Agentforce Coworker capabilities, including reusable Skills and conversation history. It announced Teams, mobile and desktop experiences for November, with scheduled tasks expected in December. Availability and packaging vary; confirm what is enabled for your organisation before planning delivery.

Read Salesforce’s announcement. The guidance below is Adaptal’s proposed evaluation approach, rather than a claim that every feature is available in every environment.

Choose one workflow worth testing

Consider a sales meeting brief, a service-case summary or a handover draft. A useful first task has a clear owner, accessible source records and an output someone can check. Avoid beginning with a process that changes financial records or sends customer communications without review.

Write down how the task is completed today, how long it takes and what makes the result acceptable. This creates a baseline for deciding whether the pilot is useful.

Five checks before connecting your team

Access

Test with an ordinary user account. Identify which customer records and connected documents the user should be able to retrieve, and test that restricted information remains restricted.

Data quality

Check ownership, record completeness and duplicate information. An articulate answer is not evidence that the underlying customer data is accurate.

Approval

Define which outputs remain drafts and which actions require a person to approve them. Record who is accountable when an answer is incomplete or wrong.

Cost

Confirm the applicable licences, usage model and expected workload. Agree a pilot budget and a way to review actual usage before extending access.

Evidence

Use representative tasks, including missing records and ambiguous requests. Review factual accuracy, time saved, correction effort and inappropriate access attempts.

Decide what happens after the pilot

Expand only when the team can explain where the tool helps and where it still needs oversight. If source data or workflow ownership is the main problem, address that first. Keep a record of the test cases, permissions and approvals so subsequent changes can be reviewed.

An existing environment may benefit from a Salesforce health check or ongoing support. A larger change to your operating processes belongs in a scoped implementation plan.