1. Acceptance and Parties
Business service. Tejma Work Order Scheduling is a business tool offered to companies and professionals (each organization, a "Customer"). Each member of an organization who uses the service (a "user") is bound by these Terms when they sign in, and a user who acts for an organization — setting up its workspace, recording its work orders, deciding on them — represents that they are authorized to do so on its behalf.
Recorded acceptance, once, for yourself. Every user must accept the current version of these Terms and the Privacy Policy for themselves before using the service: until they do, every API request and every tool call is refused with a message naming the step to take, and nothing — not even the organization's workspace — is created on their behalf. That is the only acceptance there is: nothing is accepted on an organization's behalf, and no member's acceptance covers another's. Each acceptance is recorded per version with the time it was given, the network address and client software of the request, and the user identifier that gave it. It is an append-only consent record and is kept after you leave an organization or your account is deleted.
Administrators act for the organization. Who belongs to your organization, and which Tejma Work Order Scheduling roles each member holds, is decided by your organization's administrators in Tejma Dispatcher (Section 3). Their decisions — installing this connector on a seat, granting or revoking a role, removing a member — bind the Customer.
Changes to these Terms. We may update these Terms from time to time. When we publish a new version, the service asks every user to accept it again before continuing. Material changes will additionally be announced to organization administrators through the service or by email, ordinarily at least 14 days before they take effect, except where a change is required by law or only adds a feature or option you may decline. The date at the top of this document reflects the latest revision.
2. The Service
What the service does. Tejma Work Order Scheduling keeps your organization's work-order workspace: the portals you receive work orders from, each with the ordered steps its process expects of you; every work order received, whichever portal and route it came by — the job, the site, the customer, the fee as the portal stated it, the link to the job, the requested window, the estimate, and the response deadline; the calendar check for each open order — *fit*, *conflict*, or *review* — with its reasons in plain words, the day's timeline, the suggested slot, and the alternatives; the decision on each order, the slot it was booked into, the calendar event it became, and the portal steps completed; the calendar blocks the check books around; your working hours, default job length, and travel buffer; statistics for each portal; and an audit trail of every change.
Three ways in, one set of tools. The same tools are available through the service's MCP endpoint, used by MCP clients such as an AI assistant, a Tejma Dispatcher agent, or any other MCP-compatible software; through its REST API; and through the dashboard. Whichever door is used, the same sign-in, the same roles, and the same rules apply.
A system of record you direct. The service reads no mailbox, calendar, or portal and never acts in one. Every record in the workspace is made at the direction of your members, personally or through the assistants and clients they connect: the assistant reads the portal's email and records the work order; it lists your calendar's events and syncs them as busy time; you accept or decline in the portal and tell the service what you did; the assistant creates the calendar event and stores its identifier. The service enforces the rules a careful dispatcher expects — a portal number already on file is refused rather than recorded twice, a slot is booked only when the calendar check says it fits unless you expressly allow the conflict, only an open order can be accepted or declined and only an accepted one rescheduled or completed, and a deleted order is hidden rather than removed — but it cannot know whether a record matches the portal's email, whether the calendar it was given is complete, or whether a portal has since changed or withdrawn the job. The correctness and completeness of the workspace, and every decision taken in a portal, are your responsibility.
Service evolution. We may improve, modify, or discontinue features of the service. If we discontinue the service entirely, we will give organization administrators at least 30 days' notice and a way to export Customer Content.
3. Accounts, Organizations, and Access
Sign-in. Authentication is provided through WorkOS AuthKit, under the single WorkOS application every Tejma service shares: a person signed in to Tejma Dispatcher is signed in to Tejma Work Order Scheduling with the same account. You are responsible for safeguarding your credentials and sessions. The service holds no password and keeps no list of users; it reads your identity from the signed token WorkOS issues on each request.
Access through Tejma Dispatcher. Tejma Work Order Scheduling is delivered as a connector of Tejma Dispatcher. To use it, an administrator of your organization installs this connector on a member's Dispatcher seat and grants that member one or both of its access roles there. On every request, the service asks Dispatcher whether the signed-in user's seat still has the connector installed, granted, and not parked by the seat's plan, which organization that seat belongs to, and which roles it carries; a user without such a seat, or whose grant is revoked or parked, is refused until that changes. Your use of Tejma Dispatcher — including its seats, plans, quotas, and any charges — is governed by the Tejma Dispatcher Terms of Service; Section 4 explains how the seat's plan bears on this service.
Two roles. The reader role allows the read-only tools — the dashboard, the inbox and each work order with its calendar check, slot suggestions and ad-hoc fit checks, the week view, the lists of calendar blocks and portals, your availability, portal statistics, and the change trail — and the account page. The writer role allows the tools that change the workspace — recording, updating, accepting, declining, reopening, rescheduling, completing, cancelling, and deleting work orders and marking their portal steps; adding, changing, removing, and syncing calendar blocks; setting working hours and scheduling defaults; managing portals; noting an email sync — together with the workspace's own settings (its name and time zone) and setting up the workspace of an organization seen for the first time. Full access takes both; a user with one role sees and may call only that half of the tools, and a user with neither can do nothing beyond accepting these Terms. The roles are the ones Dispatcher reports as granted to the member on this connector.
The workspace belongs to the organization, and is shared within it. Every organization has exactly one workspace, created the first time a member holding the writer role acts for it — with Monday-to-Friday, 8 am to 5 pm working hours, no portals, and the organization's identifier as its name until someone renames it. The workspace is shared: every member of your organization with the reader role sees all of it, every work order and every customer's details included, and every member with the writer role may change all of it. Another organization's records and identifiers behave as if they do not exist. Grant roles accordingly.
Accurate information. You agree to provide accurate information about your organization and to keep it current. We may suspend access for organizations that provide false information or that we reasonably believe are being used fraudulently.
4. Fees, Plans, and Quotas
Tejma Work Order Scheduling charges nothing of its own: there is no subscription, trial, seat price, usage metering, or paywall for the service itself, and nothing in these Terms creates a payment obligation to Tejma for it.
Access to it, however, is governed by your Tejma Dispatcher seat and the plan that seat is on, as described below. Any AI assistant or MCP client you use with the service may also carry charges of its own under its own terms.
Your Dispatcher grant and plan govern access. Tejma Work Order Scheduling is a Tejma connector in Tejma Dispatcher, so whether a member can use it, and how much, follows two things there. First, a holder of the organization's users role must have granted the member this connector, with one or more of its roles; revoking the grant ends the member's access at once. Second, the member's Dispatcher seat plan must have room for the connector under its cap on installed Tejma connectors; a seat over that cap — for example after a downgrade — has its newest Tejma connectors parked, and the service refuses a member whose install is parked until the plan grows, the seat fits again, or the grant is restored. When the inbox is run by a Dispatcher agent, each of that agent's executions also counts against the seat's Dispatcher execution quota and AI billing, as the Tejma Dispatcher Terms of Service describe.
Caps and quotas may change. The cap on Tejma connectors each Dispatcher plan carries, and the quotas and other limits of each plan, are set by Tejma Dispatcher and may change over time, as the Dispatcher Terms of Service describe. A change of that kind may reduce or end a seat's access to Tejma Work Order Scheduling without any fee being introduced for the service itself. Should we ever charge for Tejma Work Order Scheduling directly, we will announce it to organization administrators at least 30 days before it takes effect, and you will be able to read and export your existing workspace throughout that notice period without charge.
5. Your Workspace and Customer Content
Customer Content is yours. All records in your workspace — portals and their steps, work orders and the decisions on them, calendar blocks, working hours and settings, and notes — the checks and statistics computed from them, and the audit trail of changes to them ("Customer Content") belong to the Customer. You grant Tejma a limited, non-exclusive license to host, copy, back up, and process Customer Content solely to provide, secure, and support the service. We do not sell Customer Content, use it for advertising, or use it to train AI models.
Other people's details. The workspace naturally holds information about third parties: the name, phone number, and service address of the customer a portal sends you to; the text of a portal's message; the titles of the calendar events your assistant syncs, which may describe other jobs, other people, or your own appointments. You represent that you are entitled to record that information and to have it processed as described in these Terms and the Privacy Policy, that doing so is consistent with your agreements with the portals it came from, and that you have provided any notices and obtained any consents the laws that apply to you require.
Not your mailbox, calendar, or portal. The service holds records, not the systems they came from. It stores no email, only the fields extracted from one and its identifier; no calendar credentials, only the busy time passed to it; and no portal account — a work order may carry a link to the job in the portal, which the service never retrieves. The portal remains the system of record for the job itself, and your email and calendar remain where they are; what the service shows is only as current as the last sync your assistant ran.
Retention by design. The workspace is a history of what each portal sent and what you decided, so the service is built to keep it: deleting a work order hides it but keeps the row, declined, completed, and cancelled orders stay on file, and every insertion, change, and deletion is recorded in the audit trail with the record's values before and after. Removing content from the workspace is therefore not the same as erasing it; the Privacy Policy explains how to request full erasure.
6. Acceptable Use
You agree not to use the service to:
- access or attempt to access another organization's workspace, or use the service through a sign-in or seat you are not authorized to use;
- circumvent the roles, the policy-acceptance gate, or any other control of the service, or probe or test its security without our written permission;
- record information about customers or other people that you have no right to process, or use the service in breach of your agreements with the portals whose work orders it holds;
- keep a record you know to be false in order to deceive a portal, a customer, an insurer, or anyone else about what was received, accepted, booked, or completed, or otherwise use the service in connection with fraud;
- transmit malware, or generate automated load that degrades the service for others;
- resell, sublicense, or white-label the service without a separate written agreement with Tejma;
- use the service to build a competing product by systematic extraction of its functionality.
We may suspend or throttle access for organizations engaged in the above, and will notify an organization administrator where the law and the circumstances allow.
7. AI Clients and Your Responsibility
Tejma Work Order Scheduling makes no AI calls. The service itself calls no AI model and sends your workspace to no AI provider. AI enters only through MCP clients that you or your members connect — an assistant such as Claude, an agent you configure in Tejma Dispatcher, or any other MCP client — which read and change the workspace through the same tools a person would, under the sign-in and roles of the member who connected them, and which read your mailbox and calendar through connectors of their own that the service never touches. How the AI provider behind such a client handles what the client sends it is governed by that provider's terms and, for a Tejma Dispatcher agent, by the Tejma Dispatcher Terms of Service and Privacy Policy.
What a connected client does, you did. Every work order recorded, every decision recorded, and every calendar block synced through a connected client is attributed to the member whose sign-in authorized it and binds the Customer exactly as if that member had done it by hand. Review what your clients record, grant them only the role they need, and have your administrator revoke a seat's grant in Tejma Dispatcher when a client should no longer have access.
Guidance for assistants. We publish instructions — a "work-order dispatcher" skill — that tell an AI assistant how to use the tools carefully: never to decide for you or act in a portal; to record one work order once, keyed to the email it came from and the portal's number; never to guess a window, deadline, fee, address, or link the email does not give; to sync the calendar before presenting checks; and to read back what it recorded. They are guidance to the assistant, not a guarantee of its behaviour, and an assistant may ignore or misapply them.
AI can be wrong. An assistant may misread a portal's email, record the wrong date, window, or address, attach an order to the wrong portal, miss a deadline, sync a stale calendar, or present a conflict as a fit, and identical inputs may produce different results. You are responsible for reviewing what is recorded and for every decision you take on the strength of it.
The calendar check is arithmetic, not a promise. A *fit* means that a slot of the job's estimated length lies inside the requested window, within the working hours you set, clear of the booked time the service was given and the buffer you chose. The check knows nothing the workspace does not hold: an event not yet synced, travel that takes longer than the buffer, a job that runs over, a crew that is unavailable, or a change the portal made after its email. Treat its verdicts and suggested slots as a starting point for your own judgement, not a substitute for it.
Your portals are your business. Tejma is not a party to your agreement with any portal, home-warranty network, property manager, or facilities platform, and the service neither accepts, declines, schedules, invoices, nor submits anything to any of them: every action in a portal is taken by you, in the portal, and the service only records what you tell it. Response deadlines, authorizations, invoices, service-level requirements, penalties, and payment are between you and the portal, and the service's record of an order — its deadline, fee, and steps included — is only as accurate as what was recorded from the portal's message. The portals named in the service belong to their owners; Tejma is not affiliated with or endorsed by any of them.
8. Third-Party Services
The service interoperates with third-party services under their own terms: WorkOS (authentication), Railway (cloud hosting and the database), and Cloudflare (network edge), plus whichever MCP clients and AI providers you choose to connect. Your use of each is governed by that provider's terms, and their availability is outside our control — an outage or change at a provider may interrupt the corresponding feature. Tejma Dispatcher is our own service and is governed by its own Terms of Service; because Tejma Work Order Scheduling relies on it to confirm your seat and roles, the service refuses requests while Dispatcher cannot be reached. The portals whose work orders you record, and the email and calendar accounts your assistant reads and writes, are your own relationships and accounts, reached through connectors you authorize to your assistant and never by the service; Tejma is not responsible for their availability, their changes, or what your assistant does in them. MCP clients you connect are third-party software chosen by you; Tejma does not review, endorse, or assume responsibility for them or for what they do in your workspace.
9. Privacy and Data Protection
Our Privacy Policy describes what we collect, how we use it, what a connected AI client brings in and can see, how long we keep it, and the rights available to you; it is incorporated into these Terms. Tejma acts as the Customer's processor for Customer Content. Where the Customer's use of the service involves personal data subject to the GDPR, UK GDPR, or similar laws, a data processing agreement on terms equivalent to the Tejma Dispatcher Data Processing Agreement is available on request at the contact below.
10. Suspension and Termination
By you. You may stop using the service at any time. Your organization's administrators may revoke a member's roles or uninstall this connector from a seat in Tejma Dispatcher at any time, which ends that member's access immediately, and may ask us at the contact below to delete the organization's workspace.
By us. We may suspend or terminate access for material breach of these Terms, legal requirement, or a genuine security risk. Where practicable we will notify an organization administrator and give an opportunity to cure before termination.
After termination. Upon termination you may request an export of your Customer Content within 30 days; after that window we may delete the organization's workspace in the ordinary course, as described in the Privacy Policy. Sections that by their nature survive — ownership, disclaimers, liability limits, and indemnities — survive.
11. Disclaimers and Limitation of Liability
Disclaimer. The service is provided "as is" and "as available." To the maximum extent permitted by law, Tejma disclaims all warranties, express or implied, including merchantability, fitness for a particular purpose, non-infringement, and any warranty that the service will be uninterrupted or error-free, or that its calendar checks, suggested slots, deadlines, and statistics are accurate, complete, or sufficient for any decision.
Liability cap. Tejma Work Order Scheduling carries no fee of its own. To the maximum extent permitted by law, Tejma's aggregate liability arising out of or relating to the service will not exceed one hundred US dollars (US $100), and neither party is liable for indirect, incidental, special, consequential, or punitive damages, for lost profits, revenue, or data, or for a missed response deadline, a declined or forfeited work order, a double booking or scheduling conflict, or any penalty, deduction, chargeback, or loss of standing imposed by a portal. These limits do not apply to a party's willful misconduct or to liability that cannot be limited by law.
Indemnity. The Customer will defend and indemnify Tejma against third-party claims arising from Customer Content, from information about customers or other third parties recorded in the workspace without authority, from what connected clients do in the workspace or in your mailbox, calendar, or portals, from your dealings with any portal or customer, or from use of the service in violation of these Terms or applicable law.
12. General Terms
Governing law and venue. These Terms are governed by the laws of the State of Nevada, excluding its conflict-of-laws rules, and disputes will be resolved in the state or federal courts located in Washoe County, Nevada, which both parties consent to.
Miscellaneous. These Terms, together with the Privacy Policy, are the entire agreement regarding the service and supersede prior discussions; your use of Tejma Dispatcher is governed separately by its own terms. Neither party may assign these Terms without consent, except to a successor in a merger or asset sale. If a provision is unenforceable, the rest remains in effect. A failure to enforce is not a waiver. Notices to Tejma go to Tejma LLC, Reno, Nevada, at the contact below; notices to the Customer go to its organization administrators through the service or email on file.
Matej Meciar · Tejma LLC
