Templates, cloning, and stitching are where TaskRay's onboarding muscle lives. These prompts put that power one sentence away.
In this article:
- The template launch
- The mid-flight expansion
- The team setup
- The customer's list
- The spreadsheet-to-template build
The template launch
The moment. A deal closed, and the new onboarding project needs to be ready for the customer call this afternoon.
Try this
"Create a new onboarding project for Meridian Health from our Standard Onboarding template, starting next Monday."
What happens. Your assistant clones the template into a real project with the full tree: task groups, tasks, checklists, dependencies, and dates shifted to your start date. The same power you have always had in TaskRay, reached in one sentence.
What you need. A TaskRay license with access to Templates. You must have permission to create projects in Salesforce.
Pro tip. Ask "which onboarding templates do we have?" first if you are not sure of the exact template name.
The mid-flight expansion
The moment. The customer added a workstream halfway through, and the playbook for it already exists as a template.
Try this
"Stitch the Data Migration task group template into the Meridian Health project."
What happens. Your assistant merges the template task group into the live project, so scope changes reuse your playbooks instead of being rebuilt by hand.
What you need. A TaskRay license with access to Templates. You must have edit access to the project.
The team setup
The moment. New project, and the right people need access without a trip to Setup.
Try this
"Add Jordan Reyes to the Meridian Health project as a contributor with edit access."
What happens. Your assistant creates the contributor record, and TaskRay handles the sharing and notification the same way it does from the UI.
What you need. Any TaskRay license.
An important limit. MCP can add an existing user to a project, but it cannot provision a Salesforce or TaskRay license. The person being added must already have the required license and Salesforce permissions. Just as an unlicensed person will not appear as an option in the UI, they cannot be added here. A new license has to be set up in Salesforce first.
The customer's list
The moment. The customer emailed a few dozen tasks they want in the shared plan, with no dates and no owners, and some of them already exist under slightly different names.
Try this
"Here is the task list our customer sent: [paste the list]. Add these to the Acme Mutual Action Plan, but skip anything that duplicates a task already in the project, even if the wording differs."
What happens. Your assistant compares the incoming list against the live project, recognizes near-duplicates by meaning rather than exact wording, and creates only the genuinely new tasks. The batch queues as one approval, so you see exactly what is about to land before it does.
What you need. Any TaskRay license with edit access to the project.
The spreadsheet-to-template build
The moment. You have a spreadsheet of project structures that need to exist as TaskRay templates. Building each one by hand is hours of clicking.
Try this
"Here is the template structure: [attach spreadsheet]. Create TaskRay project templates for each, sequence the tasks so each one schedules relative to the task before it, and assign tasks to the correct queue IDs."
What happens. Your assistant reads the spreadsheet, creates each template with its full task structure, sets up the relative date sequencing across tasks, and assigns queue ownership. You get templates ready to use, with the scheduling logic baked in.
What you need. A TaskRay license with access to Templates. You must have permission to create templates in Salesforce. Works best with spreadsheets that clearly define task order and queue assignments. Keep task names to 80 characters or fewer; your assistant will flag any that exceed the limit before creating them.
Pro tip. Go one file at a time for large builds. Your assistant handles hundreds of tasks reliably in a single spreadsheet, and splitting by template type keeps sessions clean and makes any errors easier to trace.