i need an ai agent to answer the phones. find out what they need and get that info to us unless they need an estimate. if they need an estimate have them fill out the questionaire at popcornremoval.biz once that is done find out when is good for the estimate and set the appointment up in our software.

We are seeking a Voice Specialist to provide lines for cloning a voice for an AI agent. The ideal candidate will have experience in voice acting with a strong command of English. The job is simple and will take hardly any time. I will provide the lines/scripts to read. You will record them in clean audio. You will send me the raw audio files. You must consent to your recorded voice being used to create an AI voice clone for commercial phone calls. I need the voice to sound natural, calm, warm, clear, and trustworthy on the phone. The voice should feel: Mature and professional Calm and patient Clear and easy to understand Warm but not fake Conversational, not commercial Not robotic Not overly energetic Not salesy Good for older prospects to listen to on a phone call Clean phone-quality audio matters more than studio perfection. I care most about the voice sounding natural, trustworthy, and believable in a real phone conversation.

Project Overview We are building an AI-powered voice receptionist agent for a dental practice client. The agent will handle inbound calls 24/7 — booking, rescheduling, and canceling appointments, answering FAQs, and escalating complex situations to a human. The voice layer is built in Retell.ai and the orchestration/automation flows run in n8n, with integration into a dental practice management systems. This is a hands-on build role, not consulting. You will design, configure, and iterate the agent working directly with our founding team. What You'll Build: Conversational voice flows for new and returning patients (booking, rescheduling, cancellations, FAQs, insurance questions, urgent/emergency triage) Clean escalation paths to human staff when the agent can't handle the call n8n workflows connecting the voice agent to the practice management API for real-time schedule reads/writes HIPAA-conscious configurations and tool choices throughout the stack Performance tracking and iterative prompt/flow improvements based on real call feedback Seeking an Expert Who: You've built multiple production voice agents, ideally in healthcare or dental, and can own the full stack from architecture to delivery. You think critically about latency, barge-in behavior, edge cases, and HIPAA compliance — not just happy-path flows. Requirements: Deep expertise in Retell.ai — prompt tuning, latency optimization, interruption/barge-in handling, LLM selection, and cost modeling Advanced n8n automation — complex branching logic, dynamic data handling, external API integrations, and error recovery Experience with dental or healthcare organizations — you understand how practices operate, what front desks actually deal with, and how to translate that into agent logic HIPAA awareness — you know which tools and configurations are appropriate for PHI workflows Track record of full-cycle delivery: scoping → build → pilot → iteration Nice to have: Dentrix Ascend integration, NexHealth, prior AI receptionist or appointment-booking agent for a clinic/practice. 📋 To Apply, Please Answer Have you built a production voice agent with Retell.ai? If yes, briefly describe it. What's your approach to managing Retell.ai per-minute costs on an inbound call agent? Have you worked with dental or healthcare clients before? What was the workflow? Paste a relevant n8n workflow screenshot or describe your most complex flow.

Overview We run an AI voice assistant for self-storage operators. We have an internal, AI-assisted workflow for triaging call feedback — investigating what happened on a call, diagnosing the root cause in our codebase, and drafting fixes. We’re looking for someone technical to run that AI-assisted workflow day to day and help us make it better. You’ll be driving AI coding agents, reading real code to understand behavior, and improving the process and tooling itself. What you’ll do Use our AI agent tooling to work through a queue of customer feedback on AI voice calls. Read our TypeScript/Node codebase (voice-agent prompt assembly, workflow/“SOP” engine, tool implementations) to diagnose why the agent behaved a certain way — not just guess. Draft fixes: workflow-instruction edits, knowledge-base entries, or code changes via pull request with a clear verification plan. Improve the triage process itself — refine the AI agent prompts/skills, conventions, and the internal MCP tooling that powers it. Write clear, customer-facing summaries of what changed for our team to review and approve. You’re a great fit if you Read and reason about code confidently — ideally TypeScript/Node; React a plus. Have hands-on experience driving AI coding agents (Claude Code, Cursor, or similar) and understand how LLM prompts/tools/agents fit together. Think in cause-and-effect: “the agent did X because line Y / instruction Z.” Write precisely and concisely for both technical and non-technical audiences. Are process-minded — you spot the repetitive thing and turn it into a better workflow. Bonus: prompt engineering, LLM tool/agent development, or voice/conversational AI experience. How we work We’ll start with a paid trial on a small batch, then scale steady ongoing volume. To apply: Tell us about a time you used an AI coding agent to diagnose or fix something non-trivial in a codebase you didn’t write — what you did, and how you verified it worked. A link to relevant work is a plus.

Summary We're an early-stage AI startup building Hirey — an agent-to-agent marketplace that runs inside various AI tools via a plugin. Think "Upwork for AI agents": your agent finds, vets, and books the right human or agent on your behalf. We're looking for 5 AI agent enthusiasts to install our plugin (OpenClaw, Codex, Opus, Gemini), try it out, and sit for a short 10-15 minute video interview about your experience. The interview will be posted on our hirey.ai site. About 45 minutes of your time total. What you'll do Install the Hirey plugin in Codex. It connects your agent to Hirey's remote MCP server, so there's no local server, Node setup, Claude Desktop, or JSON config edit required. Setup is usually: enable the plugin, restart the AI agent you installed on. Connect to Hirey, run a sample workflow, and check out the hirey.ai page. A 10-15 minute video interview with the founding team. We'll ask about your experience with Hirey and your broader take on the AI agent/MCP ecosystem. Camera on, recorded, and published on hirey.ai — by taking part you're agreeing to be filmed and featured on our site. Who we're looking for Someone who has used AI tools in the past, especially for coding or technical tasks. You use Claude Desktop, Cursor, Codex, or similar AI dev tools regularly. Bonus: you've built or contributed to anything in the AI agent / MCP / LangChain / Claude Code ecosystem. What you get $20 flat, released via Upwork on interview completion. A feature on hirey.ai as an early voice in the AI agent space. Early access to the Hirey AI agent network if you want to keep using it. A direct line to the founding team. To apply, answer these in your proposal Have you used an AI coding tool before? Which one(s)? One sentence on a recent AI/agent project you've worked on or played with. Your timezone and earliest availability this week. Confirm you're comfortable being filmed and featured on hirey.ai. We'll respond within 24 hours and schedule interviews within 2 business days. No long applications, no portfolio review. Optimizing for speed.

Overview Transit & Flow is a fast-scaling Columbus home services company (plumbing, HVAC, drain, sewer, water heater, sump pump) building a premium, AI-powered operation. We are wiring together a set of best-in-class platforms into one self-functioning system that captures, books, reschedules, reminds, invoices, and follows up with customers automatically across phone, website chat, and Thumbtack. We need a senior integration specialist to stand this up cleanly, end to end, on a short-term contract. This is an execution role for someone who has built production voice-AI and automation systems before, not a learner. Detailed architecture blueprints will be provided to the hired contractor under NDA. What you will build A connected stack with no manual re-entry between systems: • Bland AI voice agents (several agents: inbound scheduler, after-hours and emergency handling, Thumbtack lead agent, and an outbound reminders and follow-up agent) • A website chat agent running the same booking logic in text • Thumbtack Live Connect bridged to a Bland agent via API and webhook, plus the Thumbtack lead feed into our automation bus • Quo.com as the telephony and SMS layer (call forwarding to Bland, SMS send via API, one consistent business number) • GoHighLevel CRM integration (contact sync, pipelines, nurture) • Make.com as the orchestration layer (scenarios for booking, rescheduling, reminders, estimates, invoicing, lead intake, error handling) • Scheduling, rescheduling, cancellation, and automated appointment reminders against our field service management platform (currently Jobber, migrating to OctopusPro, so platform-flexible API work is required) • Email automation including emailing and resending invoices and receipts on request Core responsibilities • Configure Bland pathways, custom tools, and webhooks that read and write to our systems mid-call (check availability, book, reschedule, cancel) • Build robust Make.com scenarios with idempotency, retries, error handling, and alerting • Integrate REST APIs and webhooks across Bland, Quo, GoHighLevel, Thumbtack, the FSM, and email • Bridge Thumbtack Live Connect to a dedicated Bland number so leads are answered live • Implement automated SMS and voice reminders with confirm and reschedule handling • Document everything and deliver a clean handoff so the system is maintainable and scalable Must-have skills • Proven production experience with a voice-AI platform: Bland strongly preferred, or Vapi, Retell, or Synthflow with transferable skill • Advanced Make.com (or n8n) including webhooks, data stores, error handling, and routing • Strong REST API and webhook integration skills, JSON, authentication, signing • GoHighLevel API experience • Telephony and SMS concepts: call forwarding, SIP or number routing, A2P • Ability to design for scale and reliability, not just a demo that works once Nice to have • Quo.com or comparable VoIP platform experience • Thumbtack pro tooling or lead-response automation experience • Home services or field service management background • OctopusPro, Jobber, or similar FSM API experience Engagement • Short-term contract, estimated 3 to 5 weeks • Milestone-based fixed price preferred, hourly considered for the right expert • Async daily updates, a few live working sessions per week • NDA and scoped system access required; you will not receive owner credentials How to apply Do not send a generic proposal. Answer these in your application: 1. Link or describe a voice-AI agent you built that booked or scheduled against a live external API mid-call. What platform, what API, what was the hardest part? 2. How do you make Make.com or n8n scenarios idempotent and resilient to duplicate webhooks and failed calls? 3. In two or three sentences, how would you bridge Thumbtack Live Connect to a voice AI agent so the agent answers the lead live? 4. Your proposed milestone breakdown and realistic timeline for the scope above. 5. How you handle client credentials and secrets securely. Strong applications that show real systems thinking move to a short paid test task before the full award.

I am building a daily AI voice call service called Still Here for seniors. Every morning, a warm familiar voice calls each member by name, remembers what they said last week, and has a real conversation — not a check-in, not a menu, not a script. A genuine morning conversation. All conversation scripts are already written. I provide everything. I need technical setup only. WHAT I NEED: • Retell AI account configured with HIPAA BAA signed • Florida phone number purchased and connected • Warm natural voice selected (must not sound robotic or rushed) • 7 conversation flow pathways built from my written scripts • Scheduled daily outbound calls at member-specified times • Call transcripts emailed after each call • Missed call alert system • Airtable integration for member management • 1-hour handover call — train me to manage everything going forward. CRITICAL FOR THIS PROJECT: Latency and voice warmth matter more than anything else. The person on the other end is a senior who may be lonely or uncertain. An awkward pause or robotic response breaks everything we are building. You must have experience with warm, natural outbound conversational agents — not just inbound IVR systems or chatbots. PLEASE INCLUDE IN YOUR PROPOSAL: • Your Retell AI experience specifically — projects completed • A phone number I can call to hear one of your Retell AI builds • Your approach to minimizing latency for natural conversation • Your estimated timeline • Confirmation you will sign an NDA before project details are shared A signed NDA is required before any Still Here materials are shared.

Create an outbound sales system for Real Estate. Should include both lead generation, ai voice calls, sms and email follow ups

Build an AI Marketing Operating System for Local Business I am an orthodontist building an internal AI platform for my practice. This is NOT a website project. The platform should: * Continuously monitor public internet sources for local conversations related to orthodontics. * Use AI to determine whether a conversation is worth engaging. * Generate suggested responses in our brand voice. * Never publish automatically. * Present every suggestion in an approval dashboard where I can Approve, Edit, or Reject. * Generate blog posts, Google Business Profile posts, newsletters, Instagram captions, FAQs, and YouTube scripts. * Track analytics and improve recommendations over time. Technologies preferred: * OpenAI API * Make.com or n8n * React / Next.js * Supabase * Airtable (acceptable for MVP) * PostgreSQL * Docker Applicants should have experience with: * AI agents * Human-in-the-loop workflows * LLM integrations * Automation * Dashboard development

Engagement Overview I am the CEO and principal attorney of a small law practice specializing in campaign finance, lobbying regulation, FARA, nonprofit law, and government ethics. My five-person team — a junior partner, two associates, and an executive assistant — recently integrated into a larger firm. I am looking for an experienced Claude/AI automation builder for a phased engagement to design, build, and deploy a suite of interconnected agents and automations. This brief covers three phases. Phase I (Inbox Triage) is the highest immediate priority and the natural starting point. Phases II and III follow sequentially. Strong candidates will be evaluated on Phase I but should demonstrate familiarity with the full roadmap. This is a paid engagement. Scope, timeline, and rate are open to discussion. Technology Stack Email: Gmail (personal Pro account — not firm infrastructure) AI: Claude (Anthropic) via MCP or API Task and project management: Notion (existing workspace; routing tables, matter tracking, and timesheet structure already in place) Calendar: Google Calendar Internal chat: Google Chat Document storage: Google Drive (primary); local hard drives on iMac and MacBook Pro (secondary) Matter management / DMS: iManage (larger firm system — integration via dedicated ingestion email address) Voice notes: Plaud (AI note-taker) Signing platform: TBD — candidates should ask during scoping Out of scope: Signal and iMessage — encrypted platforms with no API access; manual forwarding convention only Confidentiality Requirements This is a law practice. Attorney-client privilege and work product protection apply to all client communications and matter-related documents. These are not compliance checkboxes — they are professional obligations with real consequences. The successful candidate must: • Execute a non-disclosure agreement prior to engagement • Demonstrate genuine understanding of why data handling matters in a legal context — not just technically, but professionally • Never use client names, email content, routing data, or document content for training, testing, or demonstration purposes • Work exclusively within the client's authenticated accounts — no third-party data stores outside the approved stack • Design systems that minimize data exposure — process and route, do not store unnecessarily Generic proposals that do not address confidentiality specifically will not be considered.   Phase I — Inbox Triage Agent Real-time classification and routing of inbound Gmail, with a daily digest to the executive assistant. Objective The principal attorney's Gmail inbox receives high volumes of email across clients, matters, and categories of widely varying priority. The goal is an agent that processes every inbound message, classifies it, routes it to the correct person automatically, and ensures nothing drops — without overloading the executive assistant with triage work she should not be doing. Two-Stage Routing Logic Stage 1 — Sender Classification Every inbound email is classified against a tiered contact list maintained in a Notion database: MVC: Most Valuable Clients — 5 to 10 contacts. Highest priority. HVP: High Value People — 10 to 20 contacts. Some overlap with MVCs. Principal attorney, unless task-type rule applies All other clients: Roster managed in Notion with assigned attorney(s). Assigned attorney(s) per Notion client record Catch-All: Anyone not in the contact table — prospects, opposing counsel, vendors, bar association, etc. Generate executive assistant daily digest Stage 2 — Task-Type Classification (MVCs only) For MVC contacts, a second classification layer routes based on the nature of the request. Rules are client-specific. Examples: • Scheduling requests → Executive assistant • Contracts and approvals → Designated associate(s) per client record • Strategic and substantive legal matters → Principal attorney Task-type rules are defined per MVC client and must be configurable without developer involvement. Routing Table — Notion All contact and routing data lives in an existing Notion database. The agent reads from it at runtime. Required fields: • Contact name and/or email domain • Tier (MVC / HVP / Standard / Catch-All) • Assigned attorney(s) for Standard clients • Task-type override rules for MVCs The executive assistant must be able to add, edit, and re-tier contacts without touching code. This is a hard requirement. Routing Output Candidates should propose their recommended approach from among the following, based on current Gmail MCP capabilities: • Apply Gmail label and/or forward to assigned attorney's address • Create a pre-addressed draft for principal attorney review before sending • Log routing decision to Notion with email link and recommended assignee Please address this question directly in your proposal — it is a key evaluation criterion. Daily Executive Assistant Digest Once per day at a configurable time, the agent generates a digest delivered to a designated Notion page covering all catch-all emails from the prior 24 hours. Each entry includes: sender, subject, timestamp, and a one-line AI summary of the email's apparent purpose.   Phase II — 5 AM Daily Brief A structured morning brief delivered to Notion each day before 5 AM, aggregating schedule, tasks, workflow status, news, and forward-looking context. Objective The principal attorney starts each day across multiple locations and needs a single, consolidated view of what matters — professional and personal — without opening email. The brief is delivered to a dedicated Notion page and covers the sections below in the following order. Section 1 — Daily Schedule Full calendar for the day pulled from Google Calendar. All events, calls, and commitments in chronological order. Section 2 — Open Projects and Undone Tasks Two sub-sections: (a) MVC high-value work — open projects and incomplete tasks for Most Valuable Clients, filtered to substantive legal work only; and (b) Personal — all open personal projects and tasks without exception. Personal items are comprehensive by design: if it is not surfaced here, it will be forgotten. Source: Notion task and project database. Section 3 — Blocking What is the principal attorney specifically holding up? Items where others in the firm are waiting for a review, decision, approval, or action. Source: Notion matter and task records where assignee or status indicates the ball is in the principal attorney's court. Note to builder: this section requires careful logic design. The agent must infer from status fields and assignee data what is genuinely waiting on the principal attorney versus what is simply unresolved. Work with client during onboarding to define the exact field logic. Section 4 — News Digest Industry News Curated digest of overnight developments in: campaign finance law and FEC activity, election administration, lobbying regulation (federal and state), nonprofit political activity, and government ethics. Format: short summary of each item with a link to the full article. Aim for signal, not volume — 5 to 10 items maximum. US Political News 5 to 10 headlines with links covering: presidential politics, US Senate and House elections, and major gubernatorial races. Stories people are actually talking about, not wire service filler. Section 5 — Firm Workflow Matter-level status summary pulled from Notion, organized by client tier and activity: Status Definition Closed Completed yesterday Moving Action taken yesterday Paused No action yesterday Stuck No action in five or more days Client groupings: MVCs (non-high-value work), Standard clients (all work), and any other open matters. Section 6 — One Month Look Ahead Rolling 30-day forward view pulled from Google Calendar covering: regulatory filing dates and compliance deadlines, matter-level deadlines, client birthdays, holidays, and planned vacations or travel. Anything that requires preparation or awareness in the next 30 days. Section 7 — Personal Financial Summary (If Feasible) Summary of personal financial position pulled from Monarch Money, if an API or MCP connector is available. Candidates should investigate Monarch's API access and address feasibility in their proposal. If not currently feasible, this section is omitted without affecting the rest of the brief. Delivery Notion only — not email. A dedicated page refreshed each morning before 5 AM. Previous day's brief should be archived, not overwritten.   Phase III — Night Maintenance Three nightly agents that run after close of business: timesheet creation, document filing preparation, and Plaud note routing. All outputs are delivered to Notion for principal attorney review. Part 1 — Timesheet Creation Objective Each evening, the agent reviews the day's activity across three sources and populates a timesheet in an existing Notion template for the principal attorney's review and finalization. Sources • Google Calendar — all events and calls attended • Gmail sent items — emails sent that day, grouped by client/matter where inferable • Google Chat — internal messages sent, grouped by thread/matter where inferable Note to builder: Google Chat API access will need to be confirmed alongside Gmail and Calendar MCPs. Confirm availability and any OAuth scope requirements in your proposal. Output: Populated Notion timesheet using existing template structure. Principal attorney reviews each morning, adjusts entries as needed, and finalizes. The agent does not finalize — it drafts. Part 2 — Document Filing Objective Each evening, the agent surfaces documents created or edited that day for the principal attorney's review. The attorney flags finals, and the agent forwards them to the firm's iManage ingestion email address for filing. Sources • Google Drive — documents created or modified that day • Local hard drives — iMac and MacBook Pro Note to builder: local hard drive access requires a locally-running component (daemon, Claude Code instance, or folder-watching script) on each machine. Please address your proposed approach to this in your proposal. Alternative approach for consideration: a designated 'Ready to File' folder on each machine that syncs to Google Drive. The attorney drags filing-ready documents into this folder throughout the day; the agent watches the folder and processes from there. Simpler architecture, device-agnostic, and builds a consistent filing habit. Candidates should evaluate and recommend. Output: A Notion page listing all documents surfaced for that day, with document name, location, and last-modified time. Principal attorney marks finals. Agent forwards marked documents to the iManage ingestion email address. iManage filing is handled by firm IT from that point — no direct iManage API integration required. Part 3 — Plaud Note Routing and Archiving Objective: The principal attorney uses a Plaud AI note-taker on calls and meetings. Each evening, the agent pulls new Plaud summaries, routes them to the appropriate team members, archives a copy to Notion tagged to the relevant client matter, and deletes the underlying audio and transcript from Plaud's platform and the local device. Prerequisite — Plaud API Plaud API or webhook access is a prerequisite for this part. Candidates must investigate and confirm availability before scoping. If Plaud does not currently support programmatic access, this part will require a manual export step as a workaround — please address both scenarios in your proposal. Routing Logic: Similar in structure to Phase I inbox triage routing (MVC/HVP/Standard tiers with task-type overrides) but with distinct rules to be defined with the client during onboarding. Do not assume inbox triage rules apply directly. Archiving: One copy of each Plaud summary is saved to Notion as a note, tagged to the relevant client matter. Tagging logic to be defined during onboarding. Deletion: After successful routing and archiving, the agent deletes: (a) the audio and transcript from Plaud's platform via API, and (b) any local copies on the principal attorney's devices. Local deletion requires the same locally-running component described in Part 2. Candidates may propose a unified local agent that handles both Part 2 and Part 3 local operations.   What I'm Looking For Strong candidates will have: • Demonstrated experience building Claude-based automations or agents — not general AI experience • Hands-on experience with Gmail MCP, Google Calendar MCP, and Notion MCP (or equivalent API integrations) • Ability to build systems that non-technical users can maintain — editability and simplicity are as important as technical sophistication • Comfort with phased delivery — Phase I first, Phases II and III following sequentially based on performance • Experience with professional services clients (legal, financial, consulting) is a meaningful plus • Willingness to execute an NDA and work within a legally sensitive environment What to Include in Your Proposal Please address the following specifically. Proposals that do not engage with these questions will not be considered. • Your proposed technical architecture for Phase I — how you would connect Gmail, Claude, and Notion • Your answer to the Gmail MCP routing output question in Phase I (labeling vs. drafts vs. Notion logging) — what is actually supported and what do you recommend • Your assessment of Plaud API availability and your proposed approach for Phase III Part 3 • Your assessment of Monarch Money API feasibility for the Phase II financial summary section • Your proposed approach to local hard drive access for Phase III Parts 2 and 3 — daemon, sync folder, or other • A comparable project you have delivered — describe the client type, the stack, and what made it work • Your estimated timeline and rate for Phase I, and a rough order-of-magnitude estimate for Phases II and III • Confirmation that you are willing to execute an NDA prior to engagement I am looking for someone who has read this brief carefully and has a specific, informed point of view on how to build it. This is phase one of a longer automation roadmap and the right candidate will be a long-term partner, not a one-time contractor.