Device Request Process & Timeline

Device Request Process & Timeline

CleanShot 2025-06-25 at 16.07.48-20250625-200753.png


🔧 Phonism Device Support Request Timeline

1. Request Submission (Day 0)

  • A support request is submitted by a customer or partner via a device request ticket.

    • Link: Click here

  • Required info: Manufacturer, model, firmware version. In addition, please provide any existing configuration files and additional comments.

2. Evaluation & Triage (1–3 business days)

  • The request is reviewed for:

    • Relevance to current roadmap

    • Scheduling into a future sprint. Currently Phonism Sprints are 30 day cycles.

    • Compatibility with existing infrastructure

    • Volume of devices

  • Missing details may be requested at this stage.

3. Device Access or Procurement (3–10 business days)

  • Phonism must have remote access via VPN and / or receive the physical device.

4. Analysis & Development (5–15 business days)

  • Provisioning Support

    • Device profile and firmware are analyzed.

    • Initial configuration base template is created.

    • Feature support is mapped and validated.

    • Additional devices in a model family may require extended days.

    • Any manufacturer-specific quirks are handled and could extend days for development.

5. Internal Testing (3-7 business days)

  • Device is provisioned via Phonism in a staging environment.

  • Interoperability, configuration profiles, and firmware updates are validated.

6. Customer Testing (Beta) (3-7 business days)

  • Customer is asked to validate in their environment.

  • Bugs or feature gaps are logged and patched.

7. Production Release

  • Once approved, the device is added to Phonism’s supported inventory.

  • Manufacturer Documentation is updated.


⏱️ Total Timeframe

  • Standard support: ~3–5 weeks from access and / or date of delivered hardware to release.

  • Expedited (high priority or strategic partner): As little as 2-3 weeks.

  • Blocked requests: Delayed if access, documentation, or firmware is missing.