Thank you for joining us for the Field
Service Winter 26 release Q&A session.
Your host for the session,
and I'm joining I'm
joined by the product managers
from field service.
We're here to answer the questions
that you've asked in the community,
as well as some frequently asked questions
provided by our product managers.
Before we get started,
I do want to remind you to make all
your purchasing decisions
based on currently available technology.
This format is going to be super casual,
so we're going to be going through
to provide answers
to your hard hitting questions.
So let's go ahead and get started.
All right so first up
our topic is going to be in
field service set up agent and shopper.
How and when can
I access the set of agent.
is going to be available for customers
to pilot in early November.
So if a customer is interested,
it requires that a product manager enable
a permission in their org.
So if any of you customers are interested,
please reach out to your.
Yes and we will get you enrolled.
So just right around the corner
here, let's go to question number two.
Does it cost
agent force or data cloud credits?
No. For the pilot,
all customers who are in
the pilot will get access to the agent.
First priority won't be billed for them.
They will need to install the foundations
product in their work,
as they'll need access
to agent force in their environment.
So they'll need to have foundations
at least in their environment, to get
And let's look at the last question
for the setup agent here.
What parts of the implementation
does setup agent help with?
It helps with three things or three
main categories within field service.
It helps our customers design
and create work types and skills,
service territories
and scheduling policies.
So we ask a series of questions,
get some information design
and then create those records.
And John, I want to go back
to the previous question of the billing.
Don't feel limited
if there are any customers
that don't want to install foundations
in their sandbox or production.
Still, go ahead and enroll.
We will give you access to one of our logs
that you can use to pilot the capability,
so don't feel limited.
Our main goal is to get feedback
and create value for our customers.
So next we're going to go to Performance
Priming and to Tyler here.
So your first question, Tyler,
what is the difference between
performance priming briefcases
and standard briefcases?
Our performance priming briefcases
are automatically generated.
So as an admin,
you don't have to do anything.
Just make your service appointments,
assign them to technicians,
and it'll automatically get primed
if there are extra records
you'd like to prime on top of that.
That's where you can use a standard
or high volume briefcase.
One common point of confusion it's
not one or the other.
All of our briefcases work together.
They're additive.
all three of them will sum up
and go to your technicians together.
So let's go to that second question.
How do your technicians trigger
a delta sync?
One of the best parts of performance
priming is technicians
don't really have to think
about thinking anymore.
They don't actually have to trigger
the delta sync at all.
So every five minutes in the background,
the app will be polling for any changes,
and those record updates from the server
will get pulled down automatically
without any effort
from the technicians at all.
Very good. That makes it super easy.
So let's look at another question here.
How do I get access to the high volume
briefcase?
So our high volume
briefcase is specifically available
for our customers on a limited edition
performance edition and Einstein editions.
Once it's generally available,
it'll show up
just with the other briefcases
and briefcase builder has another section
for high volume briefcases.
So now let's go over to AI voice
to record, edit,
and so over to you in intarsia.
What languages are supported?
AI voice Record
edit is currently supported in English.
We are absolutely looking into supporting
additional languages in the future.
Very good. Short and sweet.
So, Dorie,
we're going to come over to you now.
Let's look at dynamic
optimization. Scaling.
Are there limitations in the beta
release in terms of resource types
supported or, appointment type supported?
So dynamic scaling supports
regular resources and crews in the beta
release as well as regular appointments
and complex work.
That means we don't support contractors on
or multi day work.
But don't worry, we're working on it
and hopefully towards
the GA release we'll be able to
support all of that as well.
So let's go to another question
for optimization scaling.
Does dynamic scaling support optimization
of both global and in day operations.
So right now in the beta release again
we support global optimization
of up to 50,000 appointments.
We do not support in day operations yet
but towards the GA release.
Again the plan is to support that as well.
It's probably going to be
a lesser of scale as the nature of in day
operations is to optimize
and there are time horizon.
But look out for
what's to come in the future.
So let's go to the next topic.
Scheduling outreach agent.
Which use cases are applicable
to the scenario?
Well, out of the box, Sean.
We support
rebooking of existing appointments
from the dispatch console as well
as scheduling plan maintenance calls.
That being said,
any customer basically can customize
and apply the service to different use
cases as, as they see fit.
And so the last topic here, agent
for scheduling supervisor view.
What is the difference
between the Omni supervisor
view and the field service
supervisor view.
So the field service supervisor view
is really tailored to the dispatcher
and their job.
It's meant for the scheduling agent
to give the dispatcher
a view of all the relevant
and incoming appointments.
The relevant topics,
and enable them to make,
smart decisions based on that
and take actions accordingly.
The Omni supervisor view
gives you more of a monitoring capability
and a more general,
and has a more general purpose.
Rather than that
which is tailored to the dispatcher.
I do want to thank all of you
for joining us today,
and to thank our product managers
for answering your questions.
We do want you to keep those questions
coming via
the Idea exchange,
and we will be back for the next release.
If you're looking for more information
on releases, go to Salesforce.com
slash releases and thanks again
and we look forward to see you next time.
