AI Agent Developer for Ongoing Projects, Arabic + English (WhatsApp, Ecommerce, GoHighLevel)

We build AI agents that handle sales and customer support conversations for businesses in the Gulf. We are putting together a small delivery team for our upcoming projects and we are looking for builders we can work with long term. First assignment starts within 2 to 3 weeks. This is not a talent pool. We have work coming and we need people ready for it. === CONDITIONS === ARABIC MATTERS A GREAT DEAL HERE. Every end customer is in the Gulf, and the agents you build will hold conversations in Gulf dialect all day. If you write Arabic at that level, say so early and show us a sample. It weighs heavily in your favour. If you do not, you can still apply, but tell us honestly how you would handle the Arabic side, because we will ask. Do not apply if: - You have not already built and launched a conversational AI system that handled real customers. We are not a place to learn on. - You want to talk to the end client. You never will. - You need daily supervision to make progress. === WHAT YOU WOULD BE BUILDING === Not every project has every piece. Each one is scoped differently and most are smaller than this list. But this is the surface, and we need people who are strong across most of it. CUSTOMER SUPPORT AND SALES AGENTS. An agent that answers, recommends and closes, in Arabic and English, in the client's own brand voice. It works across whichever channels the client already uses: WhatsApp Business API, Instagram direct messages, Instagram and Facebook comment replies, Facebook Messenger, TikTok, website chat. One conversation history per customer regardless of which channel they arrived on. We never build around a single channel, and the next client's channel mix will not be the last one's. TEXT, VOICE AND IMAGES. Customers send voice notes in dialect, photos of a product, a receipt, a damaged item, a screenshot of an order. The agent has to handle all of it and reply in the language and format the customer used. WHATSAPP BUSINESS API, DONE PROPERLY. Not a phone app bridge. Correct API setup, template submission and approval, the 24 hour service window, opt in handling, and keeping the message quality rating healthy so the number does not get throttled or restricted. Meta's policies and best practice are part of the job, not an afterthought. TWO KINDS OF CLIENT, TWO ARCHITECTURES. Some clients sell products, some sell services. A commerce build is catalogue, orders, payments and returns. A services build is booking, capacity, scheduling and no shows. They fail in different ways and they are not the same system. We need people who have built both, because we take on both. ECOMMERCE INTEGRATIONS. Salla and Zid first, because that is where GCC merchants are, plus Shopify, WooCommerce, or whatever the client already runs. Catalogue and product questions across thousands of SKUs, order status lookup gated behind identity verification, returns and exchange intake, abandoned cart recovery, post purchase review requests. PAYMENT AND FINANCIAL INTEGRATIONS. Payment link generation, confirming payment status against the gateway before an order or booking is treated as confirmed, handling the failed and pending paths, invoice and receipt flows. BOOKING AND SCHEDULING. Appointments into a live calendar with real capacity and travel time constraints, so the agent never offers a slot that cannot be served. Reminders, reschedule, cancel and no show recovery. ENQUIRIES FROM PAID CHANNELS. A large share of volume arrives from advertising, not organic messages. Click to WhatsApp campaigns, lead forms, comment to DM flows, link in bio. The agent has to pick these up with the campaign context intact, and the client has to be able to see which ad produced which booking or order. LEAD QUALIFICATION. Reading intent, budget, decision authority and timing inside a normal conversation. Not a question list. Not a form wearing a chat interface. Qualified enquiries route to booking or checkout, everything else to a defined fallback. CRM AND LIFECYCLE AUTOMATION. GoHighLevel at depth: contacts, custom fields, tags, pipelines, workflows, calendars, the v2 API. Segmentation by buying behaviour. Timed follow up sequences: went quiet after asking the price, cart abandoned, order delivered, re engagement at 3 and 6 months. Weekly conversion and performance reporting. AGENT ARCHITECTURE, AS A DISCIPLINE. This is the part that separates people. Routing and intent handling, state and context management, tool and function calling, retrieval over a knowledge base, memory and summarisation, fallback and escalation design, evaluation before release, cost and latency control, and building agents that cannot be talked into ignoring their instructions or inventing a price, a stock level or a delivery date. THE ENGINEERING UNDERNEATH. Some projects are built natively in GoHighLevel. Some need real code, Python and FastAPI with an async worker and Postgres on a VPS, with GoHighLevel as the channel and CRM layer. Most are a hybrid. We need people who can do both and can tell us which is right for a given project. Someone who only knows no code tools cannot take our harder work, and someone who dismisses GoHighLevel cannot deliver our standard work. === HOW WE WORK === - You receive a complete written brief before you start: business details, products, policies, tone, credentials, and the acceptance checklist we will test against. You will not have to chase us for information. - You never contact the end client. We are the account manager. All communication runs through us. - You build it, you test it yourself against the checklist, you document it, you hand it over. No daily check ins. - Your documentation has to be good enough that another engineer could take the project over without speaking to you. - Communication matters as much as the build. We need clear written updates, honest status, and a reply within a working day. If something is going to be late we need to know before it is late, not after. === AFTER DELIVERY IS PART OF THE JOB === This is where most freelancers lose us, so read it carefully. We are not looking for someone who builds, hands over and disappears. These systems go live and talk to real customers every day. Things break, Meta changes a policy, a client adds a product line, an integration starts failing quietly. We need to know, before you start: - How many months of support are included in your project price, and what you count as included. A bug is the system not doing what your own documentation says it does. A new feature is not a bug. - What you charge for each additional month after that. - How fast you respond when something is broken in production. We work per project, not per hour. Support is priced the same way, as a monthly figure, not an hourly rate. If you only work hourly, this is not a fit. Someone who offers unlimited free support forever has not supported a live system. Someone who offers none has not thought about what happens after launch. We are looking for the honest middle. === COMPENSATION === We pay per project, never hourly. The figure depends on scope, the skill the project actually demands, and the time it takes. It is agreed in writing before you start and paid in milestones. Typically 200 to 400 USD for a standard project and 500 to 800 USD for a complex one. Below are three projects, described precisely so we are talking about the same thing. GIVE US A PRICE RANGE AND A DELIVERY TIME IN DAYS FOR EACH OF THE THREE, plus the support months you would include and your price per extra month. 1. SIMPLE. A single location service business. Two messaging channels. The agent answers service and price questions in Arabic and English, qualifies the enquiry, books into a live calendar and sends reminders. CRM: contacts, custom fields, tags, pipeline stages. Two follow up sequences, one for people who ask the price then go quiet, one asking for a review after the visit. Built in GoHighLevel. No ecommerce, no payments. 2. MODERATE. A retailer on a GCC ecommerce platform (Salla, Zid or similar) with a few hundred products, selling through four channels including comment replies. The agent answers product questions from the live catalogue, looks up order status after verifying identity, and takes return requests. It handles voice notes and product photos. Enquiries arrive from paid ad campaigns as well as organic messages, with campaign context preserved. Abandoned cart and post purchase sequences. WhatsApp Business API set up correctly with templates approved and quality rating maintained. Pipelines and a weekly report. Hybrid build: GoHighLevel plus custom code where it is needed. 3. COMPLEX. A business running both a store with several thousand products and a booking based service arm. All channels sharing one conversation history. Live catalogue answers, order lookup behind identity verification, returns, payment link generation with payment confirmed against the gateway before an order is treated as final, and booking with real capacity constraints. Voice, text and images. Escalation and human takeover detection. Built in Python and FastAPI with an async worker and Postgres on a VPS, with GoHighLevel as the channel and CRM layer. Evaluated before release, monitored after. Tested, documented, deployed, handed over. If our range does not fit how you price, say so directly and tell us what does. We would rather have that conversation now than lose a good builder over an assumption. === THIS IS MEANT TO BE LONG TERM === We are not hiring for one job. We run projects of this shape continuously and we want a small group of people we trust, who know how we work, so that each new project is a handover rather than a hiring round. The people who deliver well get first refusal on the complex builds, which pay roughly double, and keep the ongoing support work on the systems they built. === TO APPLY === Your first line must contain three things and nothing else: your usual price range for this kind of work, your typical delivery time in days, and a link to a working system you built that we can message right now. A live WhatsApp number, an Instagram account, a chat link, or a screen recording of a real system in operation. A CV or a portfolio deck is not evidence and we will not open it. Then answer these. Short and specific. We can tell the difference between an answer written by someone who has done this and an answer written to sound right. 1. Price the three example projects above (simple, moderate, complex). A range and a delivery time in days for each. 2. For the Arabic: send us three or four lines your agent would send to a Gulf customer who opens with "بكم؟" before you know what they want. If you do not write Arabic yourself, tell us how you would cover it. 3. Have you worked with an ecommerce store before? Which platform, roughly how many products, and what did your agent actually do with the catalogue? 4. Have you set up WhatsApp Business API yourself, end to end? What broke, and what have you done to keep a number's quality rating from dropping? 5. Have you built for both product businesses and service businesses? Name one of each and say what was different about the build. 6. Have you built an AI agent in code (Python or similar), without a no code or low code builder? Which project, and what did the code do that a no code tool could not? 7. Which part of the scope above have you never done before? 8. You are running two of our projects at the same time and both clients need you the same week. What actually happens? 9. The system is live. The client says customers are complaining the agent is stupid. What is the first thing you do? 10. We deliver, then the client asks for something that was not in the brief. What do you do? 11. How many months of support are included in your project price, what do you charge per extra month, and how fast do you respond when something is broken in production? Monthly figures, not hourly. 12. Something you built for a client broke three months after you handed it over, and they came back to you. What happened, and how did you handle it? Agencies are welcome if you can meet the same terms, including no contact with our clients.