This page explains the purpose of the Revive OS web application, who uses it, what users do inside the app, why Revive OS requests Google Calendar OAuth access, and how Google user data is used, stored, protected, and deleted.
Revive OS
Revive OS is a private business web application operated by Real Automation LLC. Businesses use Revive OS to manage customer leads, customer calls, customer text messages, customer intake notes, AI receptionist workflows, team notifications, appointment scheduling, business hours, and project automation settings.
Revive OS is built for service businesses that need to respond to customers, capture missed opportunities, organize customer requests, and schedule appointments. The application is used by authorized business users such as owners, managers, office staff, service coordinators, sales staff, and team members who handle customer intake and scheduling.
Short app summary for Google reviewers
Revive OS is a business dashboard that helps companies manage leads, calls, messages, AI receptionist intake, and appointment scheduling.
Revive OS uses Google Calendar only when a business user connects their calendar. The integration lets Revive OS check appointment availability, create customer appointments, update appointment details, cancel appointments, and prevent double-booking.
Revive OS is used by service businesses and their authorized team members. Example users include business owners, office managers, receptionists, dispatchers, sales staff, and service coordinators.
What users do inside Revive OS
After logging in, authorized business users can manage customer and business workflow information inside Revive OS. The dashboard is not a public social network, public calendar, consumer messaging app, or advertising platform. It is a private operational dashboard for businesses.
- View new customer leads and existing customer records.
- Store customer names, phone numbers, email addresses, service addresses, requested services, notes, and appointment preferences.
- Review customer call summaries, text message notes, form submission details, and AI receptionist intake results.
- Track lead status such as new, pending, qualified, scheduled, disqualified, archived, or completed.
- Send internal notifications to business team members when a new lead or appointment is created.
- Manage project settings, business hours, scheduling rules, appointment lengths, allowed booking windows, and calendar preferences.
- Connect Google Calendar so Revive OS can schedule appointments into the business calendar.
Plain-language purpose of Revive OS
The purpose of Revive OS is to help businesses respond to customers faster and keep customer intake organized. When a customer contacts a business by phone, text, website form, or AI receptionist conversation, Revive OS helps turn that interaction into an organized lead record or appointment workflow.
For example, if a customer contacts an auto repair shop, garage door company, landscaping company, concrete company, home service company, or similar service business, Revive OS can help store the customer’s name, phone number, service request, address, notes, preferred appointment time, and scheduling status.
Main Revive OS features
| Feature | What it does |
|---|---|
| Lead dashboard | Lets businesses view, organize, and manage customer leads and lead status. |
| Customer intake | Stores customer names, phone numbers, addresses, service requests, notes, summaries, and appointment preferences. |
| AI receptionist workflows | Supports AI-assisted customer intake, call handling, qualification, summaries, routing, and follow-up workflows. |
| Team notifications | Sends appointment and lead information to the business team so staff can follow up with customers. |
| Appointment scheduling | Helps businesses schedule customer appointments using configured business hours, scheduling rules, and connected calendar tools. |
| Business settings | Lets businesses manage project settings, business hours, booking rules, appointment lengths, calendar preferences, and automation behavior. |
Google Calendar OAuth integration
A business user may choose to connect a Google Calendar account to Revive OS through Google OAuth. Revive OS does not require Google Calendar access for every feature. Google Calendar access is requested only for businesses that want Revive OS to help with appointment scheduling.
After a business user approves the Google OAuth consent screen, Revive OS stores the calendar connection so scheduling can continue working for that business account. Revive OS uses the connected Google Calendar only for appointment scheduling and scheduling conflict prevention.
Google Calendar actions Revive OS performs
- Check availability: Revive OS checks whether a requested appointment time conflicts with existing calendar events.
- Create appointments: Revive OS creates a Google Calendar event when a customer appointment is scheduled.
- Update appointments: Revive OS updates appointment details when the customer, business, or workflow changes the time, location, notes, customer name, phone number, address, or requested service.
- Cancel appointments: Revive OS cancels or removes calendar events when an appointment is canceled by the business or customer.
- Prevent double-booking: Revive OS checks calendar availability before scheduling so it does not intentionally book over existing calendar events.
Requested Google OAuth scopes and purpose
Revive OS requests only the Google permissions needed for account identity and appointment scheduling. The exact scopes shown on the Google consent screen may depend on the current implementation.
| Google permission | Why Revive OS uses it |
|---|---|
| Google account email / identity | Used to show which Google account is connected to the business account and to store the connected calendar identity. |
| Google Calendar availability or event access | Used to check whether requested appointment times are available and to prevent scheduling conflicts. |
| Google Calendar event creation | Used to create customer appointment events on the connected business calendar. |
| Google Calendar event update/cancel access | Used to update or cancel customer appointment events when the appointment changes. |
What Google Calendar data Revive OS may access
Revive OS may access Google Calendar information only as needed for scheduling features approved by the connected business user.
- Connected Google account email address.
- Calendar IDs or calendar identifiers needed to schedule events.
- Calendar availability and busy times.
- Calendar event titles.
- Calendar event start times and end times.
- Calendar event descriptions and appointment notes.
- Calendar event locations or service addresses.
- Calendar event attendees, if attendees are included in the appointment event.
- Calendar event IDs needed to update or cancel appointments later.
What Google Calendar data Revive OS may store
Revive OS may store limited Google Calendar connection and appointment information so the scheduling integration can function.
- Connected Google email address.
- Google OAuth access token.
- Google OAuth refresh token.
- OAuth token expiration time.
- Calendar connection status.
- Google Calendar event ID for appointments created or managed by Revive OS.
- Customer appointment details created or managed by Revive OS, such as customer name, phone number, service request, appointment time, notes, and location.
How Revive OS does not use Google user data
- Revive OS does not sell Google user data.
- Revive OS does not use Google user data for advertising.
- Revive OS does not use Google Calendar data to train general AI models.
- Revive OS does not transfer Google user data for unrelated purposes.
- Revive OS does not use Google Calendar data to build consumer profiles.
- Revive OS does not allow unrelated third parties to access connected Google Calendar data.
- Revive OS uses Google Calendar data only to provide scheduling features requested by the connected business account.
How users connect Google Calendar
- The business user logs into Revive OS.
- The user opens their business project or scheduling settings.
- The user clicks a button to connect Google Calendar.
- Google shows the OAuth consent screen.
- The user approves the requested Google Calendar permissions.
- Revive OS stores the connection status and OAuth tokens needed for scheduling.
- Revive OS can then check availability and create, update, or cancel appointments for that connected business account.
How users disconnect Google Calendar
Users can request that Real Automation LLC disconnect Google Calendar by contacting team@realautomation.ai. Users may also revoke Revive OS access directly from their Google Account security permissions page.
When Google Calendar is disconnected, Revive OS may disable or delete stored OAuth tokens so the calendar integration can no longer access the connected Google Calendar.
Data deletion
Users may request deletion of their Revive OS data or Google Calendar connection data by contacting Real Automation LLC at team@realautomation.ai. Revive OS may retain limited records where required for security, fraud prevention, legal compliance, billing records, or legitimate business operations, as described in the Privacy Policy.
Who uses Revive OS
Revive OS is intended for businesses and authorized business users. It is especially useful for service businesses that receive customer calls, missed calls, text messages, website leads, appointment requests, and follow-up tasks.
Example users include business owners, managers, office staff, receptionists, dispatchers, sales representatives, service coordinators, and employees responsible for responding to customers or scheduling work.
Company information
| Product name | Revive OS |
|---|---|
| Company | Real Automation LLC |
| Application homepage | https://reviveos.app/ |
| Contact email | team@realautomation.ai |
| Privacy Policy | https://reviveos.app/pages/privacy-policy |
| Terms of Service | https://reviveos.app/pages/terms-of-service |
Public policy pages
Revive OS provides public policy pages explaining how user data is collected, used, stored, shared, protected, and deleted.