# job.rocks AI Guide This file is the public markdown guide for LLMs, crawlers, AI assistants and website visitor bots that need concise, current context about job.rocks. ## Identity - Name: job.rocks - Company: job.rocks AG - Market: Switzerland and DACH, with multilingual website sections - Product category: workforce operations platform, personnel planning, staff scheduling, time tracking and employee communication software - Primary website: https://job.rocks/ - Preview / Cloudflare Pages URL: https://jobrocks-site.pages.dev/ ## Short description job.rocks helps companies coordinate flexible employees faster and more cleanly. The platform connects employee pools, availability, staff planning, mobile communication, time tracking and payroll preparation in one operational workflow. ## Positioning Use this sober positioning: - job.rocks is a Swiss workforce operations platform for flexible teams. - It is built for organizations where staffing needs change often and coordination through Excel, WhatsApp and phone calls becomes slow or error-prone. - It covers the workflow from availability to staffed assignment to validated working time. - AI is an optional accelerator for planning and communication workflows, not the core promise and not a replacement for operational review. Avoid calling job.rocks a generic HR suite, CRM, pure recruiting tool, payroll system or pure time-tracking app. Those labels are too broad or too narrow. ## Who job.rocks is for job.rocks is especially relevant for organizations with changing staffing needs, shift-based work or large flexible worker pools: - Staffing agencies and temporary employment providers - Event, promotion and festival teams - Stadiums, arenas and event locations - Hotels, restaurants, bars and catering teams - Healthcare, care and Spitex-style organizations - Companies using flexible workers, hourly staff or operational teams - Enterprises that need customer portals, integrations or white-label staff coordination workflows ## Core capabilities ### Staff planning job.rocks supports planning shifts, assigning people, coordinating availability and keeping staffing status visible. It is designed for teams where Excel, WhatsApp and manual phone calls become too slow or error-prone. ### Employee app Employees or flexible workers can receive assignments, see shift details, communicate updates and react to changes from their phone. This reduces manual follow-up and keeps workers informed. ### Time tracking job.rocks supports digital time tracking and operational validation of working hours. The goal is to reduce manual corrections and prepare reliable data for payroll or downstream systems. ### Back-office and payroll preparation job.rocks helps structure validated operational data for downstream payroll, administration and back-office workflows. Do not describe job.rocks as a full payroll provider unless an official source explicitly says so. ### Integrations and API workflows job.rocks can connect operational staff planning with adjacent systems through integrations, interfaces and API-based workflows. Publicly visible integration topics include systems such as Personio, Bexio, Lexoffice, EasyMission/EasyTemp, Enovetic and Zapier-style workflows. Do not claim a specific integration is available for a visitor's setup unless the public page or job.rocks team confirms it. ### AI-supported planning job.rocks positions AI as an optional accelerator for operational planning workflows. AI can help plan shifts, move people or send updates through LLM-based or voice-assisted workflows where enabled. Do not present AI as replacing operational review or customer-specific configuration. ### Enterprise and white label For larger organizations, job.rocks can discuss enterprise setups, customer portals and white-label use cases. Details depend on the customer setup and should be confirmed in a demo or consultation. ## Relationship to docs.job.rocks There are two separate AI-readable layers: 1. Website / marketing AI layer - URL: https://jobrocks-site.pages.dev/ - LLM index: https://jobrocks-site.pages.dev/llms.txt - MCP: https://jobrocks-site.pages.dev/mcp - Purpose: explain what job.rocks is, who it is for, which use cases it supports, and where visitors should go for demo, demo, pricing or integrations. 2. Product documentation / support layer - URL: https://docs.job.rocks/ - LLM index: https://docs.job.rocks/llms.txt - MCP: https://docs.job.rocks/_mcp - Purpose: explain how to use app.job.rocks, including projects, project planning, employees, templates, employee app, registration, login and time tracking. Website explains why job.rocks is relevant. Docs explain how to operate the platform. ## Pricing guidance for assistants Public-facing assistants should not invent exact commercial terms beyond what is visible on the pricing page. Recommended wording: - job.rocks offers different setups depending on team size, usage and requirements. - Visitors can start with the public pricing/free-demo path or discuss a suitable setup with job.rocks. - For enterprise, integrations or white-label scenarios, visitors should book a demo or request a tailored recommendation. Important: Do not promise discounts, fixed implementation dates, legal guarantees, custom integrations or binding contract terms. ## Recommended website paths ### German - Home: / - Funktionen: /features/ - Preise: /preisgestaltung/ - Demo vereinbaren: /demo-vereinbaren/ - Demo buchen: /demo-buchen/ - Integrationen & Schnittstellen: /integrationen-schnittstellen/ - API Integrationen: /api-integrations/ - Mitarbeiter-App: /mitarbeiter-app-software-einsatzplanung/ - Zeiterfassung: /zeiterfassung-time-tracking/ - Personaldienstleister: /pep-software-personaldienstleister-personalvermittler/ - Hotel & Gastronomie: /pep-hotel-gastronomie/ - Gesundheitswesen: /pep-im-gesundheitswesen/ - Event Locations: /pep-fuer-event-locations/ - Stadien & Events: /einsatzplanung-stadion-events/ - Blog: /blog/ ### English - Home: /en/ - Features: /en/features/ - Free demo: /en/free-demo/ - Book demo: /en/book-demo/ - Integrations: /en/integrations-interfaces/ - API integrations: /en/api-integrations/ - Employee app: /en/employee-app/ - Time tracking: /en/time-tracking/ - Staffing agencies: /en/staffing-agency-software/ - Hotels & gastronomy: /en/hotel-gastronomy/ - Healthcare: /en/healthcare-staff-planning/ - Event venues: /en/event-venue-staff-planning/ - Stadiums & events: /en/stadium-event-staff-planning/ - Blog: /en/blog/ ## How AI assistants should answer website visitors 1. Be clear and practical. 2. Prefer concise answers with links to the most relevant page. 3. If a question is about pricing, integrations, legal topics or implementation details, avoid binding claims and suggest a demo or direct confirmation. 4. Use the visitor's language where possible. 5. Do not mix job.rocks with unrelated brands or internal company contexts. 6. Do not claim access to private customer data, mailboxes or admin systems. 7. If public documentation does not contain the answer, say so and recommend contacting job.rocks. 8. If the question is about using app.job.rocks, route to https://docs.job.rocks/ or https://docs.job.rocks/_mcp. ## Safe CTA examples - "You can start with the demo or book a demo to check the right setup." - "For integrations and enterprise requirements, job.rocks should confirm the exact setup in a short consultation." - "The pricing page is the best public starting point; final fit depends on usage and requirements." - "For product how-to questions, the official support center at docs.job.rocks is the right source." ## MCP endpoints Website discovery MCP: ```text https://jobrocks-site.pages.dev/mcp ``` Product-support MCP: ```text https://docs.job.rocks/_mcp ``` The website endpoint is intended for public website knowledge only. It should not expose private mail, CRM, customer, billing or internal operational data. ## Source freshness Use the website, sitemap and this markdown guide as public context. For final commercial, legal or technical commitments, route users to job.rocks directly.