PTENES
MODULE 2.2

🧱 Internal Services

The core identity defines who Jarvis is. The services define what it does. Each service is a capability block—support, sales, documents, scheduling—and the entire system is the sum of these blocks working side by side. Here, you’ll learn to think about the solution in terms of value delivered, not tools used.

Jarvis (one system, multiple services) Customer serviceresolve the customer's issue Salesguide the purchase Documentsread and extract Scheduleschedule and check + othersnew blocks Each service is a family of problems solved — a block of capability that can be switched on or off without breaking the others.
6
Topics
~50
Minutes
Intermediate
Level
Concept
Type
Module Progress0 of 6 · 0%
1

🧱 What a service is

One service is a Jarvis capability block: an area of work that brings together everything needed to solve a type of request. It’s not a tool or a prompt — it’s the answer to the question "what kind of problem can this system solve?". Thinking in terms of services means organizing Jarvis by value delivered, not by the technology used.

🎯 Service = a family of problems

When you organize the system by service, each block gets a clear owner, a clear objective, and a way to measure whether it’s working. “Support,” “sales,” and “documents” are problem areas—and each one becomes a service with clearly defined beginning, middle, and end.

✓ Think in terms of services

  • ✓"What value does this deliver?"
  • ✓Each block has an objective and an owner
  • ✓You can turn it on and off by itself
  • ✓Grows without becoming a mess

✗ Think in terms of tools

  • ✗"What trendy tool should I use?"
  • ✗Everything mixed together in a single block
  • ✗Changing one part breaks another
  • ✗No one knows what delivers value
Service
capability block
Criterion
value, not the tool
Scope
a family of problems
Advantage
modular and measurable
2

🎬 Customer Service and Support

The service for customer support is the most common and, in general, the first one to be built. It answers questions, solves problems, and takes care of the experience of people who arrive at the system. Its greatest value is consistency: responds quickly, at any time, always to the same standard—and frees the human team from repetitive questions so they can handle difficult cases.

The cycle of good customer service

1. receives: the customer's question, on their channel
2. understands: what is the intent behind the question
3. answers: with the right information and the right tone
4. resolve_or_routes: closes the case or hands it off to a human

Illustrative outline of a customer service system — the "how" is up to the agents (topic 6).

💡 Practical tip

Start the customer service offering with the 10 questions the company gets most often. Answering those ten well already takes half the workload off the team—and quickly shows value to decision-makers.

Focus
resolve the customer's issue
Value
fast and consistent
Limit
hand off the hard part
Beginning
the most common questions
3

💰 Sales and proposals

The service for sales qualifies prospects, presents solutions, and helps put together proposals and close deals. It’s where AI directly touches the revenue of the company: guiding the buying journey well—from the first question to the proposal—changes the result at the end of the month. Unlike customer service, which solves problems, the sales service guides: it moves someone from “I’m curious” to “I want to close the deal.”

1

Qualifies

Understand whether the person has the problem the company solves—and how much it affects them.

2

Presents

Connects the person's pain point to the right solution, using their language, without pushing what doesn't fit.

3

Proposes and closes

Puts together the proposal, answers the last question, and clears the way for a "yes"—or passes it to a human salesperson.

Focus
guide the purchase
Touch
the recipe
Verb
guide, not just respond
Output
proposal and closing
4

📄 Document Analysis

The service for documents reads contracts, spreadsheets, emails, and reports to extract, summarize, and classify information. This is where AI saves the most time: it takes a large amount of material that would take a human hours to read and returns, in seconds, only what matters. The value isn’t “reading”—it’s turning a pile of text into a useful answer.

🔎

Extracts

Pulls the right data from the document (values, dates, names, clauses).

📝

Summarize

Condenses pages into a paragraph that conveys the essentials without losing meaning.

🗂️

Classifies

Organizes and labels (this one is urgent, this one is financial, this one needs review).

💡 Practical tip

Define first what you want back from the document. "Summarize this contract" is vague; "list the deadline, amount, and cancellation fee in this contract" is a service with a clear output—and much more reliable answers.

Focus
read and extract
Gain
hours → seconds
Outputs
extract · summarize · classify
Secret
request a precise output
5

📅 Scheduling and Consultations

The service for scheduling schedules appointments, checks availability, and answers questions about dates and status. It’s one of the most repetitive tasks at companies — and one of the biggest sources of friction when done by hand, with endless back-and-forth messages like "what day works for you?" Doing this well frees up time and gets rid of the feeling of being stuck in a queue.

🔁 The friction it eliminates

  • Without the service: "do you have any openings Thursday?" → wait → "only Friday" → "how about in the morning?" → wait… ten messages to schedule one thing.
  • With the service: checks the calendar, offers available times, and confirms on the spot—in a single conversation.

What the service can answer

availability: "what times are available on Thursday?"
schedule: "schedule Thursday at 3 p.m. for me"
check: "what's the status of my order?"
reschedule: "I need to move it to next week"

Illustrative recreation of the intentions a scheduling service addresses.

Focus
schedule and respond
Pain point
endless date changes
Actions
check · schedule · reschedule
Gain
resolves in 1 conversation
6

🗂️ One Service, One or More Agents

A service is delivered by one or more agents. The separation is key: the service defines the "what" (what value to deliver), and the agents handle the “how” (the work that produces this value). A simple service may have just one agent; a large service, such as sales, may have several — one that qualifies leads, another that puts together the proposal — working together toward the same goal.

The service says WHAT Agents handle the HOW Service: Sales guide the purchase agent that qualifies agent that puts together the proposal agent that answers final questions

✓ Separate service from agent

  • ✓Service = the capability (the “what”)
  • ✓Agent = the executor (the “how”)
  • ✓Replace an agent without changing the service
  • ✓Multiple agents working toward the same goal

✗ Mixing the two

  • ✗"The agent is the service" (confuses the role)
  • ✗Capability tied to a single executor
  • ✗Changing how it's done breaks what gets delivered
  • ✗Impossible to grow without redoing everything
Service
the "what"
Agent
the "how"
Relationship
1 service, 1+ agents
Next
the agents (2.3)

Self-check (optional): what is a service in Jarvis?

🎯 Module summary

✓
Service = a capability block — organizes Jarvis by value delivered, not by tool.
✓
Customer service — solves the customer’s problem quickly and consistently, anytime.
✓
Sales — guides the buying journey and directly affects revenue.
✓
Documents — extracts, summarizes, and classifies; turns a pile of text into a useful answer.
✓
Scheduling — books, checks, and reschedules; ends the endless back-and-forth over dates.
✓
Service × agent — the service defines the “what”; one or more agents handle the “how.”

Next module:

2.3 — Agents: the specialized workers who carry out the "how" within each service.