Abhishek Kumar 6d93be3ef6 fix: number pool initialization in multi telephony setup ... If there are multiple telephony configurations, the form number should be initialized from the campaigns given telephonic configuration rather than the organization default telephonic configuration.		2026-05-08 14:48:53 +05:30
..
agents	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
api-keys	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
calls	fix: number pool initialization in multi telephony setup	2026-05-08 14:48:53 +05:30
campaigns	chore: add telephony configuration docs	2026-05-02 17:37:48 +05:30
telephony-configs	chore: add telephony configuration docs	2026-05-02 17:37:48 +05:30
agents.mdx	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
api-keys.mdx	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
authentication.mdx	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
calls.mdx	chore: updatae documentation for api trigger	2026-05-04 12:46:11 +05:30
campaigns.mdx	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
errors.mdx	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
openapi.json	fix: number pool initialization in multi telephony setup	2026-05-08 14:48:53 +05:30
overview.mdx	docs: add developer and api reference tabs (#190)	2026-03-14 16:30:02 +05:30
telephony-configs.mdx	chore: add telephony configuration docs	2026-05-02 17:37:48 +05:30