Obchodn\u00fd t\u00edm \u017eije v CRM \u2014 Raynet, Pipedrive alebo HubSpot. \u00da\u010dtovn\u00ed\u010dka \u017eije v POHODE. A medzi nimi sa prepisuje: nov\u00fd z\u00e1kazn\u00edk ru\u010dne do \u00fa\u010dtovn\u00edctva, vystaven\u00e1 fakt\u00fara ru\u010dne ku kontaktu, stav poh\u013ead\u00e1vok sa zis\u0165uje ot\u00e1zkou cez kancel\u00e1riu. Tento \u010dl\u00e1nok zh\u0155\u0148a, \u010do sa medzi CRM a POHODOU d\u00e1 pren\u00e1\u0161a\u0165 automaticky, ak\u00e9 \u0161tyri cesty prepojenia existuj\u00fa a pod\u013ea \u010doho vybra\u0165.<\/p>\n
Prepoji\u0165 POHODU s CRM sa d\u00e1 v\u017edy \u2014 POHODA m\u00e1 otvoren\u00e9 XML rozhranie, ktor\u00e9 vie \u010d\u00edta\u0165 aj zapisova\u0165 v\u0161etky podstatn\u00e9 agendy. Rozhoduje sa medzi nat\u00edvnym doplnkom CRM<\/strong> (r\u00fdchle, ale \u010do vie, to vie), ru\u010dnou synchroniz\u00e1ciou exportmi<\/strong> (zadarmo, ale niekto ju mus\u00ed robi\u0165), DIY automatiz\u00e1ciou<\/strong> (Make\/Zapier \u2014 naraz\u00ed na mServer) a integra\u010dnou platformou<\/strong> (stavan\u00e1 na mieru, str\u00e1\u017een\u00e1, obojsmern\u00e1). \u010c\u00edm viac agend a \u010d\u00edm viac \u013eud\u00ed so syst\u00e9mami pracuje, t\u00fdm sk\u00f4r sa oplat\u00ed posledn\u00e1 cesta.<\/p>\n<\/div>\n POHODA komunikuje cez XML rozhranie; na priebe\u017en\u00fa synchroniz\u00e1ciu sa pou\u017e\u00edva mServer<\/a> \u2014 HTTP server, ktor\u00fd je s\u00fa\u010das\u0165ou ka\u017edej POHODY, ale be\u017e\u00ed na va\u0161om stroji a treba ho spr\u00e1vne prev\u00e1dzkova\u0165. Pri ed\u00edci\u00e1ch radu SQL a E1 sa d\u00e1 \u010d\u00edta\u0165 aj priamo z datab\u00e1zy, \u010do znesie \u010dastej\u0161iu synchroniz\u00e1ciu a v\u00e4\u010d\u0161ie objemy. Ed\u00edcie sa l\u00ed\u0161ia aj t\u00fdm, ko\u013eko paraleln\u00fdch pripojen\u00ed zvl\u00e1dnu \u2014 na tom stoj\u00ed vo\u013eba intervalu synchroniz\u00e1cie.<\/p>\n Kombin\u00e1cia, ktor\u00fa staviame naj\u010dastej\u0161ie: Raynet<\/a> ako CRM, POHODA<\/a> ako \u00fa\u010dtovn\u00edctvo. Adres\u00e1r a poh\u013ead\u00e1vky te\u010d\u00fa obojsmerne, vyhran\u00e9 obchody sa menia na objedn\u00e1vky. A ak t\u00edm \u017eije v kalend\u00e1ri, synchronizujeme aj Raynet s Outlookom<\/a> \u2014 stretnutia, \u00fapravy a ru\u0161enia v oboch smeroch.<\/p>\n Naj\u010dastej\u0161\u00ed zdroj zm\u00e4tku v praxi. Obchodn\u00edk zalo\u017e\u00ed \u201eNov\u00e1k s.r.o.\u201c, \u00fa\u010dtovn\u00ed\u010dka m\u00e1 v adres\u00e1ri \u201eNOV\u00c1K, spol. s r. o.\u201c \u2014 a integr\u00e1cia bez pravidiel vyrob\u00ed tret\u00ed z\u00e1znam. Rie\u0161en\u00edm je p\u00e1rova\u0165 pod\u013ea I\u010cO, nie pod\u013ea n\u00e1zvu, a ur\u010di\u0165, ktor\u00fd syst\u00e9m je pre ktor\u00fd \u00fadaj autoritou (faktura\u010dn\u00e9 \u00fadaje vedie \u00fa\u010dtovn\u00edctvo, obchodn\u00e9 kontakty CRM). Toto pravidlo nastavujeme pri ka\u017edej integr\u00e1cii ako prv\u00e9.<\/p>\n<\/div>\n Pri integra\u010dnej platforme sa cena odv\u00edja od po\u010dtu agend \u2014 z\u00e1kladn\u00e9 prepojenie jednej agendy vyjde pod\u013ea typu na 6\u201312 hod\u00edn pr\u00e1ce, presn\u00fd rozsah sa upres\u0148uje po \u00favodnom stretnut\u00ed. Nat\u00edvne doplnky m\u00e1vaj\u00fa mesa\u010dn\u00fd pau\u0161\u00e1l, ru\u010dn\u00e1 synchroniz\u00e1cia stoj\u00ed \u010das \u010dloveka, ktor\u00fd ju rob\u00ed.<\/p>\n<\/details>\n Pri integra\u010dnej platforme \u00e1no \u2014 ka\u017ed\u00e1 agenda m\u00e1 svoj smer a interval. Typicky: z\u00e1kazn\u00edci obojsmerne, fakt\u00fary z POHODY do CRM, objedn\u00e1vky z CRM do POHODY. Nat\u00edvne doplnky b\u00fdvaj\u00fa jednosmern\u00e9.<\/p>\n<\/details>\n mServer nie je samostatn\u00fd produkt \u2014 je s\u00fa\u010das\u0165ou ka\u017edej POHODY. Treba ho ale u v\u00e1s sprev\u00e1dzkova\u0165 a udr\u017ea\u0165 v chode; s t\u00fdm pom\u00f4\u017eeme. Pri ed\u00edci\u00e1ch SQL a E1 vieme \u010das\u0165 prenosov rie\u0161i\u0165 aj priamo cez datab\u00e1zu.<\/p>\n<\/details>\n \u00c1no. Postup je rovnak\u00fd pre \u013eubovo\u013en\u00e9 CRM s API (Pipedrive, HubSpot a \u010fal\u0161ie) \u2014 men\u00ed sa len strana CRM, strana POHODY zost\u00e1va. Kombin\u00e1cie n\u00e1jdete v katal\u00f3gu integr\u00e1ci\u00ed<\/a>.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":" Obchod \u017eije v CRM, \u00fa\u010dtovn\u00edctvo v POHODE \u2014 a medzi nimi sa prepisuje. \u010co sa medzi syst\u00e9mami pren\u00e1\u0161a, ak\u00e9 s\u00fa \u0161tyri cesty prepojenia a na \u010do si da\u0165 pozor.<\/p>\n","protected":false},"author":0,"featured_media":67157,"template":"","class_list":["post-71572","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/erpedie\/71572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/erpedie"}],"about":[{"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/types\/erpedie"}],"version-history":[{"count":1,"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/erpedie\/71572\/revisions"}],"predecessor-version":[{"id":71919,"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/erpedie\/71572\/revisions\/71919"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/media\/67157"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/sk\/wp-json\/wp\/v2\/media?parent=71572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\u010co sa medzi CRM a POHODOU pren\u00e1\u0161a<\/h2>\n
\n
\u0160tyri cesty prepojenia<\/h2>\n
\n
\u0160pecifik\u00e1 POHODY, s ktor\u00fdmi treba po\u010d\u00edta\u0165<\/h2>\n
Naj\u010dastej\u0161\u00ed pr\u00edpad: Raynet + POHODA<\/h2>\n
Jedna pasca: duplicitn\u00ed z\u00e1kazn\u00edci<\/h2>\n
\u010cast\u00e9 ot\u00e1zky<\/h2>\n
Ko\u013eko prepojenie POHODY s CRM stoj\u00ed?<\/summary>\n
Funguje prepojenie obojsmerne?<\/summary>\n
Mus\u00edm kv\u00f4li integr\u00e1cii kupova\u0165 mServer?<\/summary>\n
M\u00e1m in\u00e9 CRM ne\u017e Raynet \u2014 d\u00e1 sa to tie\u017e?<\/summary>\n