Support starts with the workflow. Whether you need help with access, device setup, a pilot workflow, proof packet output, security review, integrations, or reporting an issue, CoSkip routes support around the work your team is trying to complete.
CoSkip is built for field conditions: technicians, supervisors, admins, operations leaders, and pilot teams working through real service workflows. Use this page to find the right support path, prepare the right context, and connect to the right CoSkip resource.
Support works best when the request includes the workflow, the step, the expected result, and what happened instead.
Technician, field lead, admin, operations, IT/security, buyer, or partner.
Access, device, workflow, proof packet, integration, privacy, bug, or feature request.
Workflow name, step, job context, device, expected result, and actual result.
Internal field lead, CoSkip support, trust review, integration scoping, or pilot review.
Update workflow, review proof, clarify device issue, add product feedback, or escalate internally.
Pick the path that matches the support need. Each route starts with the workflow context so CoSkip can triage without guessing.
For operations owners, field leads, pilot admins, and implementation contacts.
Include: workflow name, pilot owner, impacted step, desired change, field feedback, and proof requirements.
Get workflow help →For technicians and field users on a phone, tablet, or field device.
Include: device, workflow, step, screenshot if available, expected result, and actual result.
Get technician help →For admins, technicians, field leads, and pilot users with access questions.
Include: email, company, role, admin contact, workflow access needed, and identity context.
Get access help →For supervisors, admins, warranty teams, operations, and customer-facing teams.
Include: proof packet or workflow reference, missing item, expected export format, and review need.
Get proof packet help →For IT, admins, operations leaders, implementation partners, and system owners.
Include: system of record, desired workflow, export format, data flow, security requirements, and timeline.
Explore integrations →For IT, legal, security, privacy, procurement, and enterprise reviewers.
Include: review deadline, data questions, required documentation, pilot scope, and reviewer needs.
View Security & Trust →For something broken, unexpected, slow, inaccessible, or unreliable.
Include: URL, browser/device, steps to reproduce, expected behavior, actual behavior, and field impact.
Report a bug →For pilot partners, field leads, technicians, admins, partners, and buyers with product ideas.
Include: workflow, user type, problem, desired outcome, current workaround, and importance.
Request a feature →For visitors or users who experience a barrier accessing CoSkip's website or services.
Include: page URL, barrier description, browser/OS, and assistive technology if relevant.
View Accessibility →Use the existing CoSkip routes for pilot access, trust review, product examples, privacy resources, and support contact. Cookie preferences remain connected to the existing consent control.
CoSkip pilots work best when support stays close to the field workflow being tested. For each issue, identify the workflow, the step, the proof requirement, the user role, and the expected outcome.
Name the workflow being tested, such as HVAC PM close-out, facilities inspection, warranty repair, or electrical troubleshooting.
Point to the step, prompt, proof requirement, exception path, or export that needs attention.
Include device, location type, field conditions, screenshots, technician feedback, and what happened.
Confirm whether required photos, notes, timestamps, exceptions, signoff, or verification are missing or unclear.
Safety, customer, jobsite, scheduling, and supervisor decisions should follow the customer's internal procedures.
Use the support path with enough detail for CoSkip to triage the issue or discuss workflow changes.
CoSkip should help technicians stay focused on the job, not spend more time fighting software. Technician support should be simple, practical, and tied to the workflow step where the issue happened.
Confirm you are signed in, assigned to the right workflow, and using the right device or browser approved by your team.
Note the prompt, step, device, field environment, and what you expected CoSkip to do.
If a photo, timestamp, note, exception, or signoff did not attach correctly, include the step and what proof was required.
Capture whether the issue happened with low signal, Wi-Fi loss, device sleep, or app/browser refresh.
Flag language, order, safety context, missing exception paths, or confusing proof requirements.
Follow your company's safety procedures and supervisor guidance. CoSkip is not a substitute for trade judgment, codes, or emergency procedures.
Capture the workflow step, device, screenshot context, expected result, actual result, and whether a supervisor was notified.
Admins and operations leaders need support paths for user access, workflow configuration, proof requirements, pilot reporting, exports, and review processes.
Proof packets are the heart of CoSkip's support model. If a proof packet is missing context, support should start with the workflow step and the evidence that should have been captured.
CoSkip integration support should clarify the target workflow, the proof packet output, the system of record, the data flow, and the security review path.
Questions about PDF, CSV, link, metadata, or other output formats.
Questions about attaching proof packets to work orders, asset records, customer records, warranty files, or inspection records.
Questions about structured events, workflow completion, exception flags, proof packet creation, or review-request events.
Questions about FSM, CMMS, CRM, document storage, analytics, identity, or custom systems.
Questions about SSO/SAML, RBAC, admin access, and access control.
Questions about data types, retention, subprocessors, DPA, and audit expectations.
Security, privacy, and legal questions often involve data types, retention settings, DPA terms, subprocessors, identity, MDM, audit logs, exports, and data subject requests. Route these questions carefully so the right reviewer can respond.
For urgent security issues or suspected vulnerabilities, use the approved security contact path in CoSkip's current trust resources. CoSkip does not publish an unapproved security alias on this page.
Review private-first architecture, field data lifecycle, enterprise controls, review resources, TOMs, and pilot security path.
View Security & Trust →Review how CoSkip describes website, pilot, and app-related data handling.
Read Privacy Policy →Review data processing terms, SCCs, TOMs, subprocessors, audit assistance, and return/deletion language.
View DPA →Review current vendors and their purposes, data types, regions, safeguards, and update options.
View Subprocessors →Use the privacy/data request path for access, deletion, correction, or other applicable privacy rights.
Submit Privacy Request →Use the accessibility page for website or service access barriers and accommodation requests.
View Accessibility →Pilot support is also product learning. A good bug report or feature request helps CoSkip understand what happened in the field, what the technician expected, what proof was required, and how the workflow should improve.
CoSkip is designed to support guided workflows and proof capture. It is not a substitute for licensed trade judgment, supervisor direction, manufacturer instructions, applicable codes, jobsite safety rules, emergency response, or customer-specific procedures.
Support is faster when the request includes the workflow, user role, step, device, expected result, actual result, and proof packet or export context.
Use the existing Contact form with the Support / existing user inquiry type. The form includes support context fields and routes the request through CoSkip's current contact infrastructure.
Privacy or data requests may require identity verification or coordination with the relevant customer/admin.
Bring enough context for CoSkip to understand the field workflow, the affected step, and whether proof capture, signoff, export, review, or security context was involved.
CoSkip does not publish a separate mature help center yet. These current resources give pilot teams, admins, buyers, partners, and reviewers the fastest useful context.
Learn how CoSkip pilots start with one repeatable workflow, sample procedures, an operations owner, and field leads.
View Pilot Program →See how photos, timestamps, notes, exceptions, signoff, and verification become a close-out record.
View Sample Proof Packet →Walk through a sample guided workflow and see how guidance becomes proof.
Try Demo →Check whether your workflows, procedures, devices, proof requirements, and pilot team are ready.
Get Readiness Score →Estimate the cost of missing proof, callbacks, paperwork, admin review, and close-out friction.
Calculate ROI →Review privacy, data handling, SSO/SAML, MDM, retention, subprocessors, and compliance roadmap resources.
View Security & Trust →Understand how proof packets, exports, APIs, webhooks, and systems of record can connect.
Explore Integrations →Route buyer, pilot, media, careers, security, partnership, or support questions through the Contact page.
Contact CoSkip →Each support module is built as an intentional product-style visual so the page remains useful without relying on fake support screenshots or broken image references.
Start with the support path that matches your issue: pilot workflow, technician app, access, proof packet, integration, security/privacy, bug report, feature request, or accessibility assistance. Include the workflow, step, expected result, actual result, and device context when relevant.
CoSkip does not publish around-the-clock coverage or fixed response-time commitments on this site. Support requests are routed by inquiry type and pilot context.
Technicians should follow their company's safety procedures, supervisor direction, manufacturer instructions, applicable codes, and emergency escalation paths. CoSkip support is for product, workflow, proof packet, access, and related questions; it does not replace field safety or trade judgment.
Include the workflow, step, proof item, missing or incorrect evidence, expected export or review path, and whether the issue affects supervisor, customer, warranty, or audit review.
Yes, route access issues through the access/login support path. Include your work email, company, role, workflow access needed, and admin contact if available.
Yes. Include the workflow name, step or prompt to change, field feedback, proof requirement, exception path, and why the change matters.
Yes, route integration or export questions through support or the Integrations page. Include the system of record, desired export format, proof packet destination, data requirements, and security constraints.
Start with Security & Trust for DPA, subprocessors, data handling, retention, SSO/SAML, MDM, and review resources. Use the support/contact path for specific security or privacy questions.
Use the bug report support path. Include URL or workflow name, device/browser, steps to reproduce, expected behavior, actual behavior, screenshots if supported, and whether the issue blocks field work or proof capture.
Use the feature request path. Include the workflow, user type, problem, desired outcome, current workaround, frequency, importance, and any proof packet or integration implications.
Yes. Use the Accessibility page or accessibility support path. Include the page URL, barrier description, browser/OS, and assistive technology if relevant.
No. The Support page can help route pilot users, admins, field leads, buyers, partners, security reviewers, and website visitors. Pilot-specific support should include pilot workflow context.
Start with the workflow, the user, the step, and the proof record. CoSkip will route support around what your field team is trying to complete.