Phone Scripts

Compare the integrations behind the interface

A phone can connect calls, messages, jobs, banking, vehicles and social features in one interface. Before choosing a design, check which framework events and companion resources the package expects. List the required apps and integrations first. A missing bridge for your voice, housing or job system can matter more than the number of included apps.

• Verify framework, voice, database and notification dependencies.
• Review the included apps and which integrations need separate resources.
• Check data migration if an existing phone already stores contacts or messages.
• Test calls, reconnects, notifications, uploads and permissions on staging.

Browse compatible resources in the ESX scripts and QBCore scripts archives. If the server follows a NoPixel-inspired stack, compare the related packages under NoPixel scripts rather than assuming every phone uses the same bridges.