Permission follows the staff role
The assigned staff role determines what Galileo can view and change. Updating that role’s Galileo permissions changes access for everyone assigned to the role.
Galileo AI employees
Give Galileo the operational tasks your team repeats: investigate records, prepare the next queue, and complete the work its role and approval policy allow.
Follow the work
A supervisor has open estimates, overdue invoices, incomplete technician forms, and a dispatch day that keeps changing. Galileo can help investigate the records and assemble the next queue of work. The operating team decides which work it can complete directly, which actions need approval, and which issues need a person.
The operations question
Ask Galileo to investigate the records behind a real operational question, then review its proposed next work in the same Nexus context.
Walk through it with usThe operating boundary
Choose the staff access profile and review policy before Galileo works with customer, job, estimate, or invoice records.
Walk through it with usAsk from the field
Ask about the business while you are away from a desk. The Nexus mobile app brings Galileo into the same place the team uses for field work, with a conversation that starts from the question you actually need answered.
Here, the request is simple: which unsold estimates have the highest value right now? That is a practical starting point for deciding where to focus follow-up. It gives Galileo a clear record type, a status to consider, and a way to prioritize the response.
This screen captures the question while the answer is still being prepared. Continue the conversation to review the returned estimates and ask for more detail before deciding what to do next. Staff access and the configured approval policy still govern the work Galileo can help carry out.
See this workflow in NexusThe reusable procedure
Save a reviewed procedure as a skill so the team can return to the same instructions, trigger, and review boundary.
Walk through it with usGalileo on mobile
Open estimates deserve attention even when you are away from the office. Ask Galileo which unsold estimates have the highest value, then review the answer from the Nexus mobile app before deciding which customer conversation should happen next.
In this demo, Leo returns five unsold estimates totaling $12,455. The response lists the estimate references and customers, explains the open pipeline, and separates sold or dismissed work from the opportunities still being considered. That context makes the list more useful than a single total.
Use the answer to choose the records to review with the team. Check the scope and the next follow-up before contacting the customer. Galileo brings the information into the conversation while your staff keeps the final decision in hand.
See this workflow in NexusTake a closer look
Can an AI employee help with the work behind the phones, dispatch board, and customer follow-up?
Galileo is a Nexus AI employee with a staff role, permissions, approval policy, task conversation, work queue, and reusable skills. Use it to investigate connected records, prepare routine follow-through, and complete allowed work without moving the operation into a separate AI app.
Can AI do useful work in Nexus while I control what it can change?
Galileo works with Nexus records using the staff-role permissions you assign. Choose how it asks for approval, give it a specific task, and follow the proposed actions and completed work in its workspace.
Choose the Nexus staff role Galileo will use. Select the business areas and actions it can access, such as reading job information, adding a note, or changing an appointment.
Select Always Ask, Accept Reversible Edits, or Autopilot Within Allowed Permissions. The policy changes how eligible actions are approved; it does not remove the boundaries of the selected role.
Identify the customer, job, appointment, or document and describe the outcome. For example, ask Galileo to create an estimate, reschedule an appointment, update invoice details, or add a job note.
If Galileo needs more information, respond in the task conversation. Confirm which record or schedule change you mean rather than asking it to guess between similar customers or jobs.
The approval card explains why confirmation is needed and shows the proposed command with its available details. Approve it to continue or deny it when the proposed change is not what you intended.
Use Work to inspect plans, pending approvals, and completed actions. Open the task conversation when you need to clarify, correct, or stop the request. The activity remains available for the staff member reviewing the result.
Ask Galileo to turn a repeated procedure into a skill. Review its instructions, allowed tools, and manual, event, or scheduled trigger. Activate the reviewed skill when ready, run it when needed, and pause it when the process should stop.
For scheduled skills, review the next run and time zone and edit supported daily, weekday, or weekly timing. The Rules area shows proposed operating choices and their scope; confirm a rule, disable it, or ask Galileo to revise it before relying on that choice again.
The assigned staff role determines what Galileo can view and change. Updating that role’s Galileo permissions changes access for everyone assigned to the role.
The approval card shows the reason confirmation is needed and the proposed action details. Approve the action to continue or deny it and explain the change you want.
Autopilot uses the actions allowed by the assigned role. Payments, refunds, credentials, and tenant administration remain outside Galileo’s access.
Open a Galileo conversation and start voice when the account supports it. Allow microphone access, speak the request, and continue clarifications or corrections in that thread. Voice can submit or steer a task, while the same permission and approval controls govern the actual Nexus actions.
A few more answers
Get clear on the steps, the customer’s view, and the setup your team will need.
No. Booking and customer communication can be part of an assigned role, but Galileo can also help with estimate follow-up, purchasing review, reporting, form creation, scheduling tasks, and other permitted Nexus work.
A scheduled skill or configured after-hours phone workflow can support work outside office hours when the account has the required access, trigger, permissions, and usage allowance. Decide beforehand what it may handle independently and where it should hand off.
Galileo can work with the Nexus records and commands allowed by its assigned staff role. It can also surface information and propose the next action. The configured role and approval policy determine what can proceed.
You choose the approval policy and the role permissions. Reviewed skills can run manually, from supported events, or on a schedule when the account has the needed autonomy access and usage allowance. Payments, refunds, credentials, and tenant administration remain outside Galileo access.
Yes. Always Ask is one available policy. Other modes allow reversible work or eligible actions within the assigned permissions, depending on the configuration.
An appointment action can change its date, times, arrival window, technicians, or duration, with the parent job schedule kept in step. Staff access and the selected approval mode determine which actions can run.
It can create jobs and estimates and add notes, as well as help interpret records. The selected staff role determines which actions it can use.
No. Payments, refunds, credentials, and tenant administration remain outside Galileo’s access in every approval mode.
Your team. Your workflow.
Bring a job your team knows well. We’ll walk through the scheduling, field work, documents, and billing that matter to your business.