> For the complete documentation index, see [llms.txt](https://efdevelopment.gitbook.io/ef-phone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://efdevelopment.gitbook.io/ef-phone/introduction.md).

# Introduction

Introducing the EF-Phone script for the QB-Core framework, designed to mimic the sleek and stunning design of the iPhone 14. With its beautiful user interface, the EF-Phone script offers a range of convenient features for players in your game.

One standout feature is the fingerprint lockscreen, providing added security to protect sensitive information. The script also includes popular payment apps such as PayPal and Paytm, allowing players to make quick payments using their in-game ID.

Stay connected with your friends and community through apps like Twitter, WhatsApp, and phone call. The Google Maps location app helps players navigate the game world with ease, while the garage app lets them manage their vehicles.

Players can also access a range of services apps, including a mail app, and many more. With the EF-Phone script, you can offer a seamless and immersive experience for players in your game.

<figure><img src="/files/6KVPGwNAAZt1FvLKUpW2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://efdevelopment.gitbook.io/ef-phone/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
