Element451 institutions have been running Bolt Agents across chat, SMS, email, and voice, answering student questions around the clock and taking real actions inside the platform. Those agents arrive knowing how to do the things every institution needs done. Start an application. Book an appointment. Answer a question about a program.

What they could not know is how your institution handles the rest.

Custom Skills changes that. An administrator writes, in plain language, when a behavior applies and what the agent should do, then attaches the action the agent should take. No code, no flow builder, and no specific feature for a specific situation. Custom Skills are generally available now, included with Bolt Agents at no additional cost.

The Part Only Your Institution Can Teach

Native skills cover what's the same at every institution. Every school manages admissions applications and coordinates advising appointments the same basic way.

What's different is everything around those standard processes. Which request-for-information form a prospective nursing student should get instead of the standard one. Whether a program is active or contracted, so enrollment doesn't break. How an after-hours call at 8 PM should route. What happens next when a student responds "no" to a question about whether they still plan to attend.

None of that is unusual. It's the daily operating detail of running an enrollment or student success team, and it differs at every institution. Until now, the agent handled what it could and staff picked up the exceptions by hand.

What This Looks Like in a Conversation

Let's take a look at three examples, drawn from patterns institutions build first.

A prospective student says they want to play on the football team. Today, your Bolt agent gives a general answer about the program and offers to share more. With a Custom Skill, your recruiting process activates. The agent gives team-specific information and shares the registration link for the next home game, so interest turns into a date on the calendar instead of a pleasant exchange.

A student says their grades are dropping and they are thinking about leaving. Today, Bolt agents can recognize the moment and respond with care, but they cannot tell anyone. With a Custom Skill, they do both. The agent offers to set up an appointment with an advisor, then raises an alert so a staff member sees the conversation and follows up. The student gets help immediately and the institution finds out the same day.

A caller asks to speak to someone about housing. Today, the agent knows to hand off, but only to one general number. With a Custom Skill, it transfers the call live to a specific number, to the caller's assigned staff member, or to another specialized agent. No callback, no voicemail, no repeating the question to a second person.

The same logic applies to parents asking about tuition, students who need an advisor in a specific program, and inbound calls that should route differently at 9am than at 9pm.

The Anatomy of a Skill

Every Custom Skill has four parts, and they are the same four parts whether the skill takes a caller to the right team or handles a one-word reply to a text message.

Name and description. What the skill is, so your team can find it and maintain it later.

Conditions. When the agent should use it. This is where you write the trigger in plain language, and where you set the hard limits on channel, schedule, and date range. Those limits are checked before the agent reasons about anything, so a business-hours skill cannot fire at midnight and a seasonal skill retires itself on the date you set.

Actions. The goal, the steps, and the rules, written the way you would brief a new staff member. Inside the actions you insert tools with an @ mention, which is how the agent schedules an appointment, transfers a call, creates a task or an alert, adds a label, shares a form or document, enrolls a contact in a workflow, or hands the conversation to a person or another agent.

Agents. Which of your Bolt Agents are allowed to use the skill, and in what order the skills are evaluated.

You're filling in a structure, not staring at a blank screen or building a flowchart.

Test It Before a Student Sees It

The obvious question about teaching an agent new behavior is what happens when it gets it wrong.

The Agent Test Console is where you find out first. It is a sandbox where you talk to your own agent across Messenger, SMS, email, and voice, and watch the skills fire. Response details show which skill matched, which ones were skipped and why, and which action would have run. Tools are simulated rather than executed, so nothing is created, nothing is sent, and no test contacts are required.

That means you can test the paths that should match and the paths that should not, adjust the wording, and re-run until the behavior is right. Publishing is a decision you make after you have seen it work, not a hope you have about it.

What You Get Today

Custom Skills are live for institutions with Bolt Agents. Starter templates cover common higher education scenarios, and selecting one gives you an editable draft to tailor and save as your own. Skills can be duplicated or moved between agents, and availability controls run channel by channel across Messenger, SMS, email, voice, and WhatsApp, on your institution's own time zone.

Where to Start

Pick one narrow, high-value thing your team handles repeatedly. Not the hardest thing, and not the whole process at once. A question that comes up constantly and has a specific right answer at your institution is the ideal first skill.

Build it, test the matching and non-matching paths, then expand once the agent behaves the way your institution expects.

If you are already running Bolt Agents, the help center has a setup walkthrough that takes you through your first skill start to finish. If you are not, a demo is the fastest way to see what an agent that follows your process actually looks like.