Review volunteer and partner interest

A community member offers time or a partner proposes working together. Collect the basic details and assign a conversation so the relationship receives a useful response.

Before you start

Use an authorized workspace with Form builder and Pipeline follow-up enabled in Plugins. Both start disabled. Choose who will review responses and own the resulting opportunities. A connected mailbox is needed only when you send a reply.

Explore the nonprofits workspace with fictional records. Use it to inspect the shared screens and simulated actions; configure real forms or provider connections in a workspace you control.

Work through this example

A fictional Common Table supporter offers to help with weekend events but has not chosen a program.

Capture. Name, email, area of interest and availability using the organization’s approved consent wording.

Decide. Have the program coordinator check the appropriate role and its onboarding requirements.

Hand off. Record the agreed next contact and responsible coordinator so the supporter receives a specific response.

Complete the workflow

1. Include a name and usable email address so the reviewed response can be linked to a customer. Open Forms and create a draft called Volunteer or partner interest. Include contact email, area of interest, availability and preferred next step.

2. Preview the form, save it and publish its share link. Submit one fictional example through that link before using it with customers.

3. Open Responses, review the example and accept the appropriate response into the pipeline. Check the matched contact instead of creating a second record for the same person.

4. Open the resulting opportunity in Pipeline. Record an owner and the next action: Assign a conversation to the relevant program owner.

5. Enable and run Pipeline follow-up from Plugins. Use its findings to review stale opportunities or overdue next actions, then update the source record. The report itself does not send a message.

Check the result

The accepted response is represented in the pipeline with the correct customer context and a recorded next action. The follow-up report gives the owner a reason to inspect a record when its update or next action becomes overdue.

Adapt it for your business

Add volunteer or partnership records through a source extension if these relationships need a lifecycle separate from opportunities.

For a coded variation, use Build an extension and include this example’s decision, owner and completion check in your development brief. Keep customer identity and task history in the shared services.

What to check

If a response cannot be accepted, check for a usable email address and whether it was already reviewed. If the report is empty, inspect its coverage and the opportunity dates. To send a reply, open the conversation and verify the sender connection and recorded send result.

Plugins must be enabled for their operations to run. Hosted infrastructure and connected providers may have costs; AI conversations use your configured model. Keep each human decision required by the action’s policy, and verify the result in the source screen before relying on it.